From: Andrew Morton <akpm@digeo.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5: ext3 bug or dying drive?
Date: Thu, 05 Dec 2002 14:03:38 -0800 [thread overview]
Message-ID: <3DEFCD3A.29C98E8D@digeo.com> (raw)
In-Reply-To: 1039123660.1433.12.camel@phantasy
Robert Love wrote:
>
> Overnight, 2.5.50-mm1 took a big stinky shit:
>
> ...
>
> Rebooted and ext3 replayed the journal and said a manual check was
> needed due to I/O error on the journal.
That'll be e2fsck saying that, when it tries to do journal replay.
I/O errors on the journal during replay not good.
Were there no I/O error messages reported from the device driver,
block, buffer or pagecache layer? Generally everyone like to have
a shout as one flies past.
> Ran fsck manually, it found a
> whole bunch of orphan inodes including some scary errors like "inode
> part of corrupt orphan inode list" or similar.
>
> Rebooted again to force another fsck to be sure, and sure enough it
> found more problems. Ugh. I started thinking bad hard drive.
>
> Back up in X, and the same dmesg error occurred again. Repeat above.
>
> Now I am in 2.4 and all seems well. So perhaps not hard drive?
Well. Changed driver, scsi layer, block layer, VFS and ext3. Could
be anywhere :(
> IBM U2W drive on a 2940U2W if it matters. UP kernel.
It would be useful to give the IO system a bit of a thrashing,
to narrow the problem down. Just a `cat /dev/sda[n] > /dev/null'
would suit.
Bottom line: dunno.
next prev parent reply other threads:[~2002-12-05 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 21:27 2.5: ext3 bug or dying drive? Robert Love
2002-12-05 22:03 ` Andrew Morton [this message]
2002-12-05 22:12 ` Robert Love
2002-12-05 22:21 ` Robert Love
2002-12-06 1:03 ` Barry K. Nathan
2002-12-06 7:01 ` Rolf Eike Beer
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=3DEFCD3A.29C98E8D@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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