[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: e2fsprogs 1.23 problem handling 2.2 version 1 format journals

On Mon, Oct 01, 2001 at 11:16:28AM -0600, Andreas Dilger wrote:
> This is a known problem of older 2.2 journal code.  It forgot to zero out
> the rest of the superblock when updating the journal format, so there is
> garbage in now-used fields.  This problem was fixed in later ext3-2.2 code.

On Tue, 2001-10-02 at 12:58, Stephen C. Tweedie wrote:
> Correct, but it's probably most reasonable to assume that those fields
> are "reserved" (ie. must be zero unless defined in the future) for v2,
> but "unused" for v1.  I don't think that e2fsprogs should ever look at
> these fields for a v1 superblock, and it will just continue to cause
> trouble for people with old journals if we do.

Except it looks to me as though the upgrade code is *not* zeroing out
those fields (from an attempt yesterday when I saw the problem to do a
V1->V2 upgrade using a 2.2 kernel).  This means ignoring the misset
fields just leaves a bomb in place to explode when the journal is
upgraded (at this point e2fsck explodes when it sees the journal).

Time to have a dig into that code...


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]