Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#21764 - [initscripts] /etc/rc.d/netfs contains fuseblk, which is used for NTFS

Attached to Project: Arch Linux
Opened by Rogutės (rogutes) - Saturday, 20 November 2010, 19:58 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 04 April 2011, 07:27 GMT
Task Type Bug Report
Category Initscripts
Status Closed
Assigned To Aaron Griffin (phrakture)
Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


The filesystem list in /etc/rc.d/netfs contains fuseblk, but ntfs-3g uses this
type for its mounts. So if rc.conf had DAEMONS="daemon_using_ntfs netfs", NTFS
would be unmounted before stopping the daemon_using_ntfs. This is probably very
rare, but I thought that reporting shouldn't hurt anyone...

Additional info:
* initscripts-2010.07-1.tar.xz
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 04 April 2011, 07:27 GMT
Reason for closing:  Won't fix
Additional comments about closing:  see the last comment
Comment by Sébastien Luttringer (seblu) - Friday, 04 March 2011, 01:52 GMT
start netfs before your daemon doesn't fix? It's not just a bad order in your DAEMONS?

I don't quickly find a way to make difference between fuseblk as ntfs-3g and fuseblk as another underlying fs.
Comment by Rogutės (rogutes) - Saturday, 05 March 2011, 19:42 GMT
If I recall correctly, daemon_using_ntfs was deluge (or transmission). Changing the order to DAEMONS="netfs daemon_using_ntfs" might solve the problem, but I cannot confirm, because I am not using initscripts (I have seen and reported this during testing). Nevertheless, I think that this bug is still valid, because a user cannot know that 'netfs' will try to unmount NTFS filesystems.
Comment by Sébastien Luttringer (seblu) - Sunday, 03 April 2011, 14:26 GMT
1) Archlinux user have to be aware of its system configuration and make choice accordingly. Think KISS.
2) fuseblk (and not ntfs) can be a network filesystem, so we have to treat like this (worst case).
3) With our sysv initscripts is complicated to properly handle this.