When you install ntfs-4g on Arch, it creates a symlink in /usr/bin/mount.ntfs, so I think all ntfs-mounts are redirected to it.
I hope that's a typo - or else I want to know where this mysterious 4g version is
Though seriously, and I genuinely don't know. Since ntfs is built in to the kernel, which would take precedence when specifying ntfs - the kernel driver or the linked ntfs-3g?
]]>When you use "ntfs" you are using a different driver than that provided by ntfs-3g. Instead, you are using the kernel driver, which is simply "ntfs". ntfs-3g sits on top of the kernel fuse driver and is completely separate from the ntfs driver. As such, amending the ntfs-3g wiki would be incorrect.
When you install ntfs-3g on Arch, it creates a symlink in /usr/bin/mount.ntfs, so I think all ntfs-mounts are redirected to it.
Typo: ntfs-4g
There have been a number of fuse bugs introduced in the most recent kernels, if you use git to build your kernel, in which case you may want to subscribe to the fuse dev mailing list (or at least browse around it) to see if perhaps any of the (many) patches recently posted are likely to help you. Certainly one bug that I reported WRT ntfs-3g on fuse has since had a patch made available.
As for your fstab entry, have you tried varying your entry using the disk UUID and changing the mount parameters? Mine works fine with:
UUID=XXXXXXXXXXXXXXXXXX /mnt/Data ntfs-3g gid=users,fmask=113,dmask=002 0 0
/dev/sdb1 /mnt/windows ntfs nofail,user,rw 0 2
I use that with nfs in a local home network
]]>UUID=... /daten ntfs-3g defaults 0 0
The problem is about the type parameter of /etc/fstab. Using my home server and its ntfs partition I discovered that if I identify the ntfs partition with the 'ntfs-3g' parameter, like in the wiki, the partition is inaccessible, unmounted and the fstab isn't completely processed. But if I identify that with the 'ntfs' parameter it works perfectly as expected.
I can corret that wiki page only modifying that parameter if confirm that.
]]>