[SOLVED] NTFS Operation Not Supported (45)

ewok wrote:
I'll forward this to our build engineer and see what he can do.

Hi Ewok - Since about a week has passed I just wanted to check whether you ever heard back from your build engineer?

In the meantime another Readynas developer kindly built the package containing the bugfix for me ntfs-3g_2010.10.2AR2-1readynas-1_sparc.deb. I have been testing with this version and it solves the issue. With this fix it seems possible to retain ownership, permissions and ACLs (just like is possible with an EXT3 drive). This means that there are no more errors when running either cp -p or rsync -aAv.

By the end of this I realized that the existing Readynas Perl scripts (e.g. /frontview/bin/backup) would never work correctly with NTFS since they always use the -p option for cp and the -A option for rsync, both of which are invalid options for a filesystem that (prior to this fix) would not even allow chmod/chown. Probably the only reason that we didn't see these errors before was that the mount option "silent" was acting to suppress the errors. Interestingly the /frontview/bin/backup does contain a "FAT32 compatibility mode" that switches off the ownership/permissions/acl options for rsync but it looks like no such support was ever implemented for NTFS backups.

The only remaining questions/issues now are:
1. Where is the file on the Readynas that defines the mount options for ntfs-3g (I can't find it and it's not in /etc/fstab)?
2. We need to add the usermapping mount option (see NTFS-3G manual) and point it to a file somewhere on the main ext3 filesystem containing

::S-1-5-21-3141592653-589793238-462643383-10000

At present I have manually created the UserMapping file on my NTFS drive inside a ".NTFS-3G" directory (which ntfs-3g checks for when it mounts the device). This works but you would probably be better off using the usermapping option for your official Netgear solution so that users can simply plug in any NTFS drive, and ownership, permissions and ACLs will work out-of-the-box.
3. When can this fix be rolled out to the rest of the Readynas community?

Thanks,

Mark