public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Huey (Hui) <billh@gnuppy.monkey.org>
To: adilger@clusterfs.com
Cc: "Bill Huey (Hui)" <billh@gnuppy.monkey.org>,
	mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: ext3 journal/IDE problems ? (softirq + sched assert ?)
Date: Fri, 9 Aug 2002 02:34:55 -0700	[thread overview]
Message-ID: <20020809093455.GA1000@gnuppy.monkey.org> (raw)
In-Reply-To: <20020809063725.GB12482@clusterfs.com>

On Fri, Aug 09, 2002 at 12:37:25AM -0600, Andreas Dilger wrote:
> On Aug 08, 2002  21:04 -0700, Bill Huey wrote:
> > What's going on with this ?
> > 
> > I get:
> > EXT3-fs error (device ide0(3,5)): ext3_free_blocks: bit already cleared for block 753210
> > :
> > :
> > EXT3-fs error (device ide0(3,5)): ext3_free_blocks: bit already cleared for block 753273
> > ext3_free_blocks: aborting transaction: Journal has aborted in __ext3_journal_get_undo_access<2>EXT3-fs error (device ide0(3,5)) in ext3_free_blocks: Journal has aborted
> 
> Looks like you got a block of zeros from disk when it should have been a
> block bitmap, or your filesystem is otherwise corrupted.  You need to do
> a full fsck on this filesystem.
> 
> As for cause, I have no idea.  IDE DMA, IDE cables, memory, kernel bug...

It's certainly a kernel bug. This machine has been reliable for years with
stable kernels and I started to run the 2.5 series over the last couple
of days just to test out the softirq stuff (+ preempt) and latency. I
applied Mingo's patch for a recent scheduler assertion bug and it looks
like some kind of race is possibly happening in the IDE layer.

And Mingo, yes, the patch you sent me did help, but it looks like there's
other problems.

Thanks

bill


  reply	other threads:[~2002-08-09  9:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09  4:04 ext3 journal/IDE problems ? Bill Huey
2002-08-09  6:37 ` Andreas Dilger
2002-08-09  9:34   ` Bill Huey [this message]
2002-08-09 15:09 ` Greg Fitzgerald
2002-08-10  4:19   ` Bill Huey

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=20020809093455.GA1000@gnuppy.monkey.org \
    --to=billh@gnuppy.monkey.org \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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