cat /proc/mounts revealed:
...
/dev/sdb1 /mnt/usb1 ntfs ro,sync,dirsync,nodev,noexec,noatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1 0 0
/dev/sdb2 /mnt/usb2 ntfs ro,sync,dirsync,nodev,noexec,noatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1 0 0
/dev/sdc1 /mnt/usb1 ntfs ro,sync,dirsync,nodev,noexec,noatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1 0 0
/dev/sdc2 /mnt/usb2 ntfs ro,sync,dirsync,nodev,noexec,noatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1 0 0
/dev/sda2 /mnt/usb2 ntfs ro,sync,dirsync,nodev,noexec,noatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1 0 0
...
So why the hell were all the ntfs partitions mounted at /mnt/usb1 and /mnt/usb2 ?
Well... I got this udev rule from the wiki to automount usb devices, and apparently, udev decided to mount all the ntfs devices all of a sudden. I don't get it, as it used to work.
Well, I removed the rule, and after a reboot everything was back to normal. In any case, if I modify the rule to only check from sdd on (leaving sda-sdc alone, it should work again...
]]>As of today, without anything changed in fstab or anywhere, I can't mount 3 of 4 ntfs partitions anymore. It goes like this:
[root@Bluerabbit shapeshifter]# mount -a
ntfs-3g-mount: mount failed: Device or resource busy
ntfs-3g-mount: mount failed: Device or resource busy
ntfs-3g-mount: mount failed: Device or resource busy
Now this is the relevant part of my fstab:
UUID=E674268B74265E95 /mnt/ntfs-partitions/s-500-music ntfs-3g uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_GB.utf8,noatime 0 0
UUID=EC50614B50611E18 /mnt/ntfs-partitions/s-750-stuff ntfs-3g uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_GB.utf8,noatime 0 0
UUID=C066F50F66F506C6 /mnt/ntfs-partitions/s-750-space ntfs-3g uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_GB.utf8,noatime 0 0
UUID=CCE62C2FE62C1C68 /mnt/ntfs-partitions/s-200-archive ntfs-3g uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_GB.utf8,noatime 0 0
And it's sooo weird, really. The third partition (s-750-space) gets mounted without problems when running mount -a. I can also umount it. But after that, I _cannot_ mount it with this command:
mount -t ntfs-3g /dev/disk/by-uuid/E674268B74265E95 /mnt/ntfs-partitions/s-500-music/ -o uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_GB.utf8,noatime
even though this is _exactly_ the same as the line in fstab! What the F***!?! I can still mount it when running mount -a again. How can this be?
I also ran lsof on all the /dev and /mnt paths and nobody is using it.
I can mount all of these partitions using mount -t ntfs, but of course I lose writing support etc. Why has ntfs-3g stopped working just like that, and why does it _not_ fail on this _single_ partition (space) when using mount -a? It's so weird and I can't explain why this is happening
Does anyone know the key to this mystery? Please...
]]>