public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Antti Salmela <asalmela@iki.fi>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: ext3 assertion failure and oops, 2.4.18
Date: Tue, 21 May 2002 10:37:32 -0700	[thread overview]
Message-ID: <3CEA85DC.8623C6B8@zip.com.au> (raw)
In-Reply-To: <20020521114244.GA29043@otitsun.oulu.fi>

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.

-

      parent reply	other threads:[~2002-05-21 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 11:42 ext3 assertion failure and oops, 2.4.18 Antti Salmela
2002-05-21 11:57 ` Henrique de Moraes Holschuh
2002-05-21 17:37 ` Andrew Morton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CEA85DC.8623C6B8@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=asalmela@iki.fi \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox