Bug 184125 – sys-fs/ntfs3g-1.616-r2 prevent fsck and mount to work properly

• Product: Gentoo Linux
• Status: VERIFIED NEEDINFO

[Description DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-03 18:49:07 UTC]

root@moon_gen_2:~# fsck /dev/hdd1
fsck 1.40 (29-Jun-2007)
fsck: fsck.ntfs-3g: not found
fsck: Error 2 while executing fsck.ntfs-3g for /dev/hdd1
root@moon_gen_2:~# file -s /dev/hdd1
/dev/hdd1: Linux rev 1.0 ext3 filesystem data (large files)
root@moon_gen_2:~#

but:
root@moon_gen_2:~# fsck.ext3 /dev/hdd1
e2fsck 1.40 (29-Jun-2007)
/dev/hdd1: clean, 1072522/14663680 files, 21521479/29304560 blocks
root@moon_gen_2:~#

=> means fsck got in trouble because of sys-fs/ntfs3g

root@moon_gen_2:~# emerge -vp sys-fs/ntfs3g sys-fs/e2fsprogs
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild   R   ] sys-fs/ntfs3g-1.616-r2  USE="-suid" 0 kB
[ebuild   R   ] sys-fs/e2fsprogs-1.40  USE="nls -static" 0 kB

dhp@moon_gen_2:~$ equery b /sbin/fsck
[ Searching for file(s) /sbin/fsck in *... ]
sys-fs/e2fsprogs-1.40 (/sbin/fsck)

dhp@moon_gen_2:~$ equery f sys-fs/ntfs3g |grep bin
/bin
/bin/ntfs-3g
/sbin
/sbin/mount.ntfs-3g

Thats right, there are no fsck.ntfs-3g installed at all.

Worse: after
emerge -C ntfs3g
problem persists !!!

Re-merging ntfs3g then sys-fs/e2fsprogs does not help.

[Comment 1 DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-03 18:50:06 UTC]

Created attachment 123801 [details]
/tmp/strace.log

emerge --info here:
http://bugs.gentoo.org/attachment.cgi?id=123724

[Comment 2 DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-03 18:52:32 UTC]

Same problem with mount:

root@moon_gen_2:~# mount /dev/hdd1 /mnt/arch2
hangs, and shall be killed with
killall -9 mount

# mount -t ext3 /dev/hdd1 /mnt/arch2
works fine.

My systems start fine because I do not have any auto-fs line in /etc/fstab

[Comment 3 DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-03 18:54:06 UTC]

Created attachment 123803 [details]
/tmp/strace_mount.log

First strace was for fsck. Here is mount attempt.

[Comment 4 Jakub Moc (RETIRED) 2007-07-03 19:38:09 UTC]

Kindly attach your fstab.

[Comment 5 DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-03 19:53:07 UTC]

Created attachment 123815 [details]
/etc/fstab

[Comment 6 Jakub Moc (RETIRED) 2007-07-03 19:56:45 UTC]

Well, then change it to 0 0, not 0 2 - since there's no fsck anywhere in ntfs3g.

[Comment 7 DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-03 20:30:54 UTC]

Do you have enough info to proceed bug ?

(In reply to comment #6)
> Well, then change it to 0 0, not 0 2 - since there's no fsck anywhere in
> ntfs3g.
> 

Fstab is not a problem. I was talinkg from the beginning about manual mount.

[Comment 8 Jakub Moc (RETIRED) 2007-07-03 20:33:56 UTC]

(In reply to comment #7)
> Fstab is not a problem. I was talinkg from the beginning about manual mount.

And? Why are you instructing the thing to fsck the filesystem if there's no such feature available?! Does it work w/ 0 0 or not?
 

[Comment 9 DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-03 20:39:56 UTC]

(In reply to comment #8)
> Does it work w/ 0 0 or not?

(In reply to comment #2)
> My systems start fine because I do not have any auto-fs line in /etc/fstab
> 

I said: despite of bug, box starts well because I specify exact FS on FSTAB; other friends who use autofs on every line would have encountour problems.

Fact is: it bugs on CLI, so please stop asking about fstab, since it is counter-indicative to this bug. "0 0" vs "0 2" is thus an off-topic debate.

[Comment 10 Jakub Moc (RETIRED) 2007-07-03 20:44:11 UTC]

Could you answer the damned simple question? AFA - it works just fine here unless I stick nonsense to fstab.