Hi, You make some good points. I wonder what the "right" fix is?
I certainly think the user should not be stopped from booting and then get the inconsistent filesystem message over and over again as I do. Perhaps GRUB should offer to 'replay' the filesystem after discovering that the filesystem is "inconsistent". I am not sure what other choices there are since the kernel and the initial boot filesystem are presumably not loadable? john On Tue, 5 Sep 2006, Vladimir V. Saveliev wrote: > Hello > > On Tuesday 05 September 2006 00:30, [EMAIL PROTECTED] wrote: > > On Mon, 04 Sep 2006 23:33:27 +0400, "Vladimir V. Saveliev" said: > > > after unclean shutdown journal reply is necessary to return reiserfs to > > > consistent state. Maybe GRUB did not do that? > > > > A case can be made that GRUB should be keeping its grubby little paws off > > the filesystem journal. It's a *bootloader*. It's only purpose in life is > > to load other code that can make intelligent decisions about things like > > how (or even whether) to replay a filesystem journal. > > Yes, I did not say that grub has to replay a journal, I just tried to guess > why grub failed to boot and why things went ok after fsck. >
