Hi folkes, this DroboApp replaces the jpfilename.tgz I have submitted earlier.
DroboShare uses Paragon ufsd driver to mount NTFS filesystems.
Paragon ufsd, by default translates all non-ascii filenames to ascii equivalent characters.
When Japanese filenames are read via DroboShare, this filename translation feature of ufsd corrupts Japanese filenames.
When filenames are corrupted, smbd is unable to share them.
[*]As the result, all Japanese filenames disappears when NTFS volume is shared via DroboShare.
How to fix this problem:
Paraon ufsd driver has [iocharset] option that lets you decide how to handle foreign character sets.
See: http://free.ntfs-linux.com/options.htm for valid mount options
When iocharset=utf8 is selected, Japanese filenames are parsed correctly, and can be shared via smbd.
Things to note:
The filename translation feature takes effect not only at read time, but also when a new file is written to NTFS volume.
When a new Japanese filename is written via DroboShare on improperly mounted NTFS volume, these files will be written to NTFS volume with corrupted filename translations.
These corrupted filenames can be read as normal as long as you continue to use DroboShare to access them.
These corrupted filenames will show up garbled if Drobo is directly connected to PC.
This issue makes integration of the iocharset fix into next DroboShare firmware problematic since it might render already corrupted NTFS volumes unreadable.
If this DroboApp is applied, the already corrupted filenames will appear garbled even when read thru DroboShare.
How to install:
[*]Drop jp_ntfs_mount.tgz on DroboApps folder, reboot DroboShare.
How to uninstall:
[*]Erase jp_ntfs_mount from DroboApps folder, reboot DroboShare.
This droboapp will function only at boot time.
New volumes attached to DroboShare at runtime will not be re-mounted unless you re-run the script.
Log files will be left at: