Messages in this thread | | | Date | Tue, 21 May 2002 10:37:32 -0700 | From | Andrew Morton <> | Subject | Re: ext3 assertion failure and oops, 2.4.18 |
| |
Antti Salmela wrote: > > I can reliably reproduce an assertion failure and oops in ext3 by simply > restarting cyrus21, if directories used by cyrus have +j flag set with > chattr. Filesystem was mounted with default journalling mode data=orderded, > kernels tested were 2.4.18 and 2.4.19-pre3-ac4. Recent -pre or -ac kernels > wouldn't compile with my .config. > > Assertion failure in journal_revoke() at revoke.c:330: > "!(__builtin_constant_p(BH_Revoked) ? constant_test_bit((BH_Revoked),( > &bh->b_state)) : variable_test_bit((BH_Revoked),( &bh->b_state)))" > > I'll capture whole oops if requested. > > I found two similar cases from lkml archives, but they were left > unresponded (atleast lkml wasn't cc'ed). I couldn't judge from changelogs if > this problem has been already fixed. > > http://groups.google.com/groups?selm=2446DD7E.7F1AEC90.00A5E169%40netscape.net&output=gplain > http://groups.google.com/groups?as_umsgid=%3C2446DD7E.7F1AEC90.00A5E169%40netscape.net%3E&lr=&hl=en >
It seems that mixing journalling modes in this manner doesn't work. Please turn off +j for the while - we'll aim to fix this in 2.4.20.
- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |