[Bug 432237] Re: difficult to recover from filesystem errors

[Dave Martin]

Hi... rebooted again on armel:

Now, boot does resume after the mountall-shell exits *if* the shell
exits with status zero.

However, I still have a couple of issues:

1) A "filesystem last mounted in future" error is still treated as
serious enough to interrupt the boot process and require interaction via
mountall-shell.  My view is that this is not appopriate because this may
well happen when Windows fiddles with the clock on a dual-boot system,
or when there's some other RTC problem. The novice user may not have a
good idea what to type in the maintenenace shell anyway.  The problem
will persist across boot until the system is sufficiently convinced to
mount the fs read-write  My suggestion would be that if the only
apparent error with the root filesystem is that it was mounted in the
future, boot should proceed, although a warning is appropriate.  This
appears to have been the Jaunty behaviour.

(My ulterior motive is that we still have a lot of RTC problems with
armel development hardware so I hit the problem on virtually every boot
anyway...)

2) If the mountall-shell exits with non-zero exit status, boot does not
resume:

init: mountall-shell main process (749) terminated with status 1
<...hang...>

 This is unlikely to be appropriate: the default exit status of a shell
is simply the exit status of the last command executed... which was not
necessarily fsck. I believe fsck can exit with non-zero status for
various non-fatal situations anyway?  It's necessary to quit the shell
with "exit 0" to work around this... again, the novice user will have no
clue about that.

-- 
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs