On Fri, 20 Apr 2001, Boris Popov wrote:
> On Thu, 19 Apr 2001, John Baldwin wrote:
>
> > It needs more work, too. If you try to use an old fsck with the new kernel,
> > then the old fsck will clobber some new variables in the superblock. Then the
> > new kernel will panic later on instead of doing a sanity check on the new
> > values in the superblock and falling back to defaults if they are bogus. This
> > is a major POLA bug and the changes shouldn't go into 4.x unless this is fixed.
> > This breaks the recommended method of updating stable by doing the installworld
> > after rebooting into a new kernel.
>
> On other hand, it makes some troubles if filesystem is shared
> between 4.x and -current :)
>
> --
> Boris Popov
Hm, something just struck me.
a) Why is fsck checking fields that it doesn't know as anything other
than filler?
b) When it says that the alternate superblock doesn't match, is that
really true? If so, why isn't that being updated?
Of course the kernel should sanity check the values so it doesn't panic,
but making fsck not louse up future filesystem changes seems prudent as
well. (If that's feasible.)
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
