mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
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 08:21:08 -0400	[thread overview]
Message-ID: <20041020122108.GC12780@ns.snowman.net> (raw)
In-Reply-To: <20041020024342.GA9260@mail.13thfloor.at>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

* Herbert Poetzl (herbert@13thfloor.at) wrote:
> On Tue, Oct 19, 2004 at 06:01:00PM -0400, Stephen Frost wrote:
> > 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 ...

Hmm, that's a good thought, though I have to say I'd really like to get
a comment from the ext3 folks.  This is also a production server, so I'd
kind of like to minimize the downtime. :)

> > 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?

Yeah, I've mounted it as ext2 for now.  It's been working fine so far.

	Stephen

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-20 12:21 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
2004-10-20 12:21         ` Stephen Frost [this message]
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=20041020122108.GC12780@ns.snowman.net \
    --to=sfrost@snowman.net \
    --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