This is a bug in both ntfs-3g and fuse. Fuse 2.7.0 has fixed it and that
version is a requirement for this functionality for any fuseblk type fuse
file systems.
It's planned that the next release of ntfs-3g will also fix this issue
which will work with fuse 2.7.0 and later (it's not possible to fix it
for earlier fuse releases).
If you already have fuse 2.7.0 then a workaround can be
ntfs-3g /dev/sda11 ~/mnt/nt/ -o user=<username>
then fusermount -u will work.
In the long run fusermount will be eliminated and umount(8) can be used
instead. This requires kernel support on which Miklos Szeredi is already
working on.
ntfsmount works because it uses the unsafe 'fuse' fstype for block devices
which can result corruptions, data or volume loss if the device is detached
or powered down right after unmount since the kernel buffers aren't ensured
to be flused to the disk. You can make fusermount -u work with ntfs-3g the
same unsafe, risky way if you downgrade the fuse kernel module to a 2.5.x
or your kernel to a prior 2.6.20 version.
Szaka
--
NTFS-3G Lead Developer: http://ntfs-3g.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
