Bugzilla – Bug 145400
boot.localfs: Tries to check r/w mounted systems
Last modified: 2006-02-02 11:25:46 UTC
since udev mounts and fscks the filesystems, boot.localfs should not do it itself. Otherwise boot.localfs will check the r/w mounted filesystems, fsck will return an error value and boot stops. This just happened with three beta2 test installations. I have a quick hack in aaa_base: --- etc/init.d/boot.localfs +++ etc/init.d/boot.localfs @@ -63,6 +63,8 @@ # A return code of 2 or larger indicates failure. FSCK_RETURN=$? test $FSCK_RETURN -lt 4 + # XXX: 16 is returned if filesystem is r/w mounted + test $FSCK_RETURN -eq 16 && FSCK_RETURN=0 rc_status -v1 -r if test $FSCK_RETURN -gt 1 -a $FSCK_RETURN -lt 4 ; then # if appropriate, switch bootsplash to verbose This worked in my limited tested and should let us ship beta2. But we need a proper solution.
insserv is kaputt. your patch is likely wrong.
no, insserv is correct. boot.localfs has "Required-Start: boot.udev". the problem is fsck, it needs a new option to ignore mounted filesystems (like what is possible with "-R" for "/", but implemented better ...) hare is looking at the issue right now.
Please consider to move the house-keeping stuff from 'boot.localfs' (e.g. after '# clean up') to some place *before* 'boot.udev'...
no, most of this needs to run _after_ the filesystems are mounted.
*** Bug 145620 has been marked as a duplicate of this bug. ***
I've added a new option '-m' to fsck which causes fsck to ignore any mounted devices and to return no error if the filesystem is mounted. Rudi, boot.localfs should be adapted to take advantage of this flag.
Rudi, remember to remove the hack in aaa_base as well!
The hack was added between 'test' and 'rc_status' which made boot.localfs wrongly report failed. The trigger for this problem was /lib/udev/mount.sh. It should deal only with devices that have mount option 'hotplug' in fstab. This is now fixed and submitted.
*** Bug 146469 has been marked as a duplicate of this bug. ***
boot.localfs will call fsck with an added "-m" option now. the hack was removed.
*** Bug 146776 has been marked as a duplicate of this bug. ***