Re: problems read/write mounting of NTFS
- From: Bob McGowan <bob_mcgowan@xxxxxxxxxxxx>
- Date: Mon, 20 Aug 2007 16:55:57 -0700
Bob McGowan wrote:
Bob McGowan wrote:Krzysztof Lubański wrote:On Fri, 2007-08-17 at 14:03 -0700, Bob McGowan wrote:But, it was formatted with NTFS and I was not able to write to it[...]
I've also adjusted the associated options in /etc/fstab, but I still can't write to the disk.
The standard NTFS kernel driver and ntfsprogs have only a limited
write support. E.g. the kernel driver only allows to change existing
files, but without changing their length.
I then thought I should try the FUSE based tools, so I removed the ntfsprogs package and libntfs9 that it depends on and tried to install ntfs-3g. But it depends on 'libfuse2 (>=2.6), but all that's available in Etch is 2.5.3-4.4, which is already installed. [...]
NTFS-3G is not in stable yet, try installing it from
http://backports.org/. It will surely allow you to write.
That's the rub - I did try to install NTFS-3G, from backports, but it has the dependency mentioned (on libfuse2 >=2.6), which didn't get resolved by the installer.
I'll check backports again, and see if the libfuse2 library is there. If so I'll try installing it "manually" and report back.
OK, fuse 2.6 and libfuse 2.6 are on backports.org, but I had to download the deb files manually and used dpkg to install them. After that, the ntfs-3g package installed just fine.
Now, to see about using it ;)
Thanks for the help.
Well, closer, but not quite there...
I'm using kernel 2.6.18-5-686, which has the fuse driver, but it's not full featured. I get this warning:
WARNING: Deficient Linux kernel detected. Some driver features are
not available (swap file on NTFS, boot from NTFS by LILO), and
unmount is not safe unless it's made sure the ntfs-3g process
naturally terminates after calling 'umount'. If you wish this
message to disappear then you should upgrade to at least kernel
version 2.6.20, or request help from your distribution to fix
the kernel problem. The below web page has more information:
I've downloaded the source code for fuse version 2.6.5, compiled the driver only, and installed it. The warning message is gone.
And I can mount the disk device rw as me. The problem is, I can't unmount it ;(
mount reports this for the device:
/dev/sde1 on /media/ntfs type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
/dev/sde1 /media/ntfs ntfs-3g rw,user,noauto 0 0
I don't see the "user=rmcgowan" that I'm used to seeing when I mount a VFAT formated device. I believe that's part of the problem, as 'man mount', under 'user' states the name of the user who mounted the device is saved, so they can unmount it.
By setting the "users" option (note plural), any user is allowed to unmount. This allows me to do so, but it would be nice to know no one else can do it.
Description: S/MIME Cryptographic Signature