mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof "Sierota (o2.pl/tlen.pl)" <Krzysztof.Sierota@firma.o2.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [BUG] kernel BUG at fs/jbd/checkpoint.c:646!
Date: 13 Sep 2004 11:11:12 +0200	[thread overview]
Message-ID: <1095066672.1754.17.camel@rakieeta> (raw)
In-Reply-To: <20040913020143.12983b51.akpm@osdl.org>

W liście z pon, 13-09-2004, godz. 11:01, Andrew Morton pisze: 
> Krzysztof "Sierota (o2.pl/tlen.pl)" <Krzysztof.Sierota@firma.o2.pl> wrote:
> >
> >  the following bug is present on kernels: 2.6.7-mm6, 2.6.9-rc1-mm1,
> >  2.6.8.1-mm3. If any testing would be needed I can trigger it here in the
> >  matter of hours.
> > 
> >  Oops from 2.6.8.1-mm3 attached.
> > 
> >  Hope that someone will be able to find a solution for this.
> > 
> >  tia,
> >  Krzysztof
> > 
> > 
> > [2.6.8.1-mm3-oo1  text/plain (2745 bytes)]
> >  Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:646: "transaction->t_forget == NULL"
> 
> You're using data=journal?  If so, you'd best turn it off.
> 
> I'm not able to reproduce this, as usual.  It's on my list of things to ponder.

Yes, that is the case. I hit this bug here every 5 hours or so on 2-3 servers.
Guess I'll turn the data=journal off, for now. If you'd like to get more
info on this I can run modified kernel here if that would help.

Thank you,

Krzysztof.


      reply	other threads:[~2004-09-13  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11  1:28 Krzysztof Sierota (o2.pl/tlen.pl)
2004-09-13  9:01 ` Andrew Morton
2004-09-13  9:11   ` Krzysztof Sierota (o2.pl/tlen.pl) [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=1095066672.1754.17.camel@rakieeta \
    --to=krzysztof.sierota@firma.o2.pl \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®