David Gibson wrote:
> It seems like there are two main issues here. First, what is getting
> the dates wrong so that fsck reports the inconsistency on the
> filesystem. It sounds like that is covered in one of the other bugs
> referenced.
>
> Second problem, is why is mountall just jamming up and not dropping back
> to a shell to allow manual fscks. I have defeintely seen this
> behaviour. For some reason when I hit the timestamp inconsistency on /
> and /boot, mountall died on the failing fsck and prompted for a root
> shell. However on another (custom) mount from fstab, it seemed like it
> jammed up mountall's fsck queue. mountall kept running, did not drop to
> a shell, but never attempted to fsck anything after the thing which
> failed - including /home.
>
>
Finally someone got it right. Since I filed my bug, most seem to close
an eye or two, and tell me and us that everything is hunky dory (after
some kernel update). It isn't. Asking how many hours one is off UTC is
the wrong question. Seriously. The wrong mindset. It must not matter at
all. Let it be 01-01-1970, and it still needs to come back either with a
proper check (why not, by the way?), or at least try mountall, and drop
to a console. It does neither. The latter is a serious bug, pointing to
badly audited code, and a failure to degrade gracefully. The former is
still a bug, because the file system isn't too corrupt to easily recover
the journal: The previous shutdown was clean. Therefore, there is zero
reason to not come back easily properly on its own, without even
dropping to a rescue console.
So we have three bugs actually: The third one is the getting wrong of
the dates.
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432070
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
