Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

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!
Tasklist

FS#25377 - initscripts can't mount filesystems at boot

Attached to Project: Arch Linux
Opened by Pavel (Alsvartr) - Wednesday, 03 August 2011, 04:48 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 03 August 2011, 12:27 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
For some reason latest initscripts-2011.07.3-1 can't mount filesystems. It fails to mount / in rw and then all the local filesystems.
But if I replace all "mount" calls with "/bin/mount" in /etc/rc.sysinit and /etc/rc.d/functions than all works as expected.

alsvartr@bust > echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl


Additional info:
initscripts-2011.07.3-1
This task depends upon

Closed by  Tom Gundersen (tomegun)
Wednesday, 03 August 2011, 12:27 GMT
Reason for closing:  Won't fix
Comment by Jan de Groot (JGC) - Wednesday, 03 August 2011, 05:53 GMT
What does "which mount" give on your system? Looks like you're having an additional mount binary installed in /usr/local/bin or /usr/bin.
Comment by Pavel (Alsvartr) - Wednesday, 03 August 2011, 06:23 GMT
That's right. Thanks for the tip.

alsvartr@bust > which mount
/usr/local/bin/mount
alsvartr@bust > pacman -Qo /usr/local/bin/mount
error: No package owns /usr/local/bin/mount

alsvartr@bust > which mount
/usr/bin/mount
alsvartr@bust > pacman -Qo /usr/bin/mount
error: No package owns /usr/bin/mount

My bad.
Comment by Jan de Groot (JGC) - Wednesday, 03 August 2011, 07:15 GMT
To fix your problem, you should remove those. The more foolproof solution is to change rc.sysinit to use full paths instead of what it does now.
Comment by Pavel (Alsvartr) - Wednesday, 03 August 2011, 08:44 GMT
Yep, already removed. Everytning is fine now.
Comment by Tom Gundersen (tomegun) - Wednesday, 03 August 2011, 12:23 GMT
The assumption is that if you install a mount binary in path, then you want it to be used. Notice that we ignore /usr/local/*, which is where you should but stuff you compile yourself for testing purposes. FYI, our PATH is set at the top of /etc/rc.sysinit.

Loading...