Re: [2.4.22-rc1] ext3/jbd assertion failure transaction.c:1164

From: Pascal Schmidt
Date: Tue Aug 26 2003 - 10:59:43 EST


On Tue, 26 Aug 2003, Pascal Schmidt wrote:

> Yes. Running fsx directly on my ext3 /home partition gets me the
> BUG within a few seconds, with the exact same backtrace as below.
> There don't seem to be any jbd changes from -rc1 to final 2.4.22,
> so I assume the problem exists in 2.4.22 as well.

I've just updated to 2.4.22-rc3 (since bkcvs doesn't seem to have
final 2.4.22 yet). There, the BUG is not triggered. Instead I get
tons of these:

Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 2472965)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 2472966)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 2472967)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 2472952)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 2472954)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 2472955)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 71346)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 66050)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 66050)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 66049)
Unexpected dirty buffer encountered at do_get_write_access:616 (03:07 blocknr 66050)

These messages pile up as long as I run fsx.

Again, this is on an ext3 partition mounted with data=journal.

--
Ciao,
Pascal

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/