mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: LKML <linux-kernel@vger.kernel.org>,
	Vserver <vserver@list.linux-vserver.org>
Subject: Re: [Vserver] PROBLEM: Oops in log_do_checkpoint, using vserver
Date: Wed, 20 Oct 2004 04:43:42 +0200	[thread overview]
Message-ID: <20041020024342.GA9260@mail.13thfloor.at> (raw)
In-Reply-To: <20041019220100.GB12780@ns.snowman.net>

On Tue, Oct 19, 2004 at 06:01:00PM -0400, Stephen Frost wrote:
> * Stephen Frost (sfrost@snowman.net) wrote:
> > * Herbert Poetzl (herbert@13thfloor.at) wrote:
> > > have seen that too, once in a while, but there where
> > > some changes in 2.6.9, so maybe trying 2.6.9-rc4
> > > (or soon final) with vs1.9.3-rc3 (not much changed
> > > here, see delta for details) would be a good check
> > 
> > Ok.  I had been planning on moving to 2.6.9 and 1.9.3 as soon as both
> > were final.  Guess I can try the RC releases though. :)
> 
> Alright, I got the same oops w/ 2.6.9 and vs1.9.3-rc3:
> 
> Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:361: 
> "drop_count != 0 || cleanup_ret != 0"

you can split up this assertion into

 - drop_count != 0
 - cleanup_ret != 0

and fail on that (or just output those values
before you panic) ... this might give some
deeper insight into the issue ...

> 
> I noticed someone else had this problem too:
> 
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123137

hmm, so that kernel should not be vserver related
at all, so I'd say something with the ext3 journal
is broken ...

> I also followed up on that w/ my oops from 2.6.8.1.
> 
> I also upgraded to 0.30.195, though I don't think that (or vserver in
> general, really) is related to this oops.

yeah, probably not, I think the vserver changes 
just make the oops more likely (or simply the 
increased load does)

> If there's anything else I can do to help get this resolved, please let
> me know..  This is the only problem I'm having with this server now,
> other than this it's behaving pretty nicely. :)

maybe until it gets fixed, mounting the ext3
without journal might help here?

best,
Herbert

> 	Thanks,
> 
> 		Stephen



> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver


  reply	other threads:[~2004-10-20  2:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18  3:25 Stephen Frost
2004-10-18 11:55 ` [Vserver] " Herbert Poetzl
2004-10-18 12:20   ` Stephen Frost
2004-10-19 22:01     ` Stephen Frost
2004-10-20  2:43       ` Herbert Poetzl [this message]
2004-10-20 12:21         ` Stephen Frost
2004-10-21  9:12           ` Jan Kara

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=20041020024342.GA9260@mail.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vserver@list.linux-vserver.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
Powered by JetHome