Hi,
On Mon, Oct 28, 2002 at 11:13:57AM +0000, Mark Hazell wrote:
> I got your addresses from the MAINTAINERS file in the kernel source
> tree, so apologies if i should have sent this somewhere else first.
>
> Summary: I was copying 700mb of data to my ext3 RAID-1 39gig filesystem
> (2.4gig free according to 'df') yesterday, when the kernel spewed out
> the lines at the bottom of this email.
The start of this is just anonymous disk corruption -- there's no way
I can tell how it happened, but this:
> Oct 28 02:44:14 recondo kernel: attempt to access beyond end of device
> Oct 28 02:44:14 recondo kernel: 09:00: rw=1, want=38708548,
> limit=38708544
looks like you've got a corrupt indirect block on disk somewhere which
is pointing to illegal data blocks off the end of the disk.
That said, ext3 should survive such corruption. It fails to do so
because of the core block IO code, which in generic_make_request(),
does:
if (maxsector < count || maxsector - count < sector) {
/* Yecch */
bh->b_state &= (1 << BH_Lock) | (1 << BH_Mapped);
and this has the unfortunate side effect of zapping key ext3 metadata
in the buffer state bits, leading up to
> Oct 28 02:44:15 recondo kernel: Assertion failure in
> __journal_remove_journal_he ad() at journal.c:1732: "buffer_jbd(bh)"
> Oct 28 02:44:15 recondo kernel: kernel BUG at journal.c:1732!
when ext3 next comes across the buffer that it knows it owns, but
which has been cleared of ext3 metadata.
The patch below fixes it for me (it's easy to reproduce --- just set
up an ext3 filesystem on an LVM device and then lvreduce it while live
to force half of the filesystem off the end of the device.)
Folks, just which buffer flags do we want to preserve in this case?
--Stephen
This archive was generated by hypermail 2b29 : Fri Nov 15 2002 - 22:00:25 EST