[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141201220534.GA4619@wallace>
Date: Mon, 1 Dec 2014 17:05:34 -0500
From: Eric Whitney <enwlinux@...il.com>
To: "Darrick J. Wong" <darrick.wong@...cle.com>
Cc: Eric Whitney <enwlinux@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: xfstests failures w/ metadata_csum
* Darrick J. Wong <darrick.wong@...cle.com>:
> Hi Eric,
>
> Could you remind me which xfstests are failing in 3.18-rc3+ with metadata_csum
> enabled? I think you said generic/034, generic/321, and generic/322, but were
> there more?
Hi Darrick:
The other failing test is generic/325 - you've got the others right. Note that
I may be an xfstests version ahead of xfstests-bld, so depending on what you're
running, you may not see all of those. (Gonna stick closer to xfstests-bld
from now on.) The failures are the same in the inline data test scenario.
Thanks for looking at this!
Eric
>
> AFAICT the ext4 mount fails because it can't load the journal, and the journal
> can't replay because jbd2_descr_block_csum_verify() fails; the 034 test appears
> to drop all the writes related to the umount. recovery.c doesn't say anything
> when the journal descriptor block fails csum verification, though it should.
> Not sure why we end up with corrupt-looking descriptor blocks.
>
> The reason why this appears in -rc3 is because that's when we added the patch
> that forces journal_checksum on whenever metadata_csum is on, and I guess
> few people were testing journal_checksum with xfstests before that.
>
> --D
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists