From: Robert Love <rml@tech9.net>
To: akpm@digeo.com
Cc: linux-kernel@vger.kernel.org
Subject: 2.5: ext3 bug or dying drive?
Date: 05 Dec 2002 16:27:40 -0500 [thread overview]
Message-ID: <1039123660.1433.12.camel@phantasy> (raw)
Overnight, 2.5.50-mm1 took a big stinky shit:
EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #243371: rec_len % 4 != 0 - offset=1688, inode=243681, rec_len=109, name_len=27
Aborting journal on device sd(8,1).
ext3_abort called.
EXT3-fs abort (device sd(8,1)): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sd(8,1)) in start_transaction: Journal has aborted
EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #243371: rec_len % 4 != 0 - offset=1688, inode=243681, rec_len=109, name_len=27
EXT3-fs error (device sd(8,1)) in ext3_setattr: Journal has aborted
EXT3-fs error (device sd(8,1)) in start_transaction: Journal has aborted
EXT3-fs error (device sd(8,1)) in start_transaction: Journal has aborted
Nothing particularly interesting was going on (mostly idle X desktop).
I woke up and noticed the fs was mounted ro. The above was in dmesg.
Rebooted and ext3 replayed the journal and said a manual check was
needed due to I/O error on the journal. 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?
IBM U2W drive on a 2940U2W if it matters. UP kernel.
Robert Love
next reply other threads:[~2002-12-05 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 21:27 Robert Love [this message]
2002-12-05 22:03 ` 2.5: ext3 bug or dying drive? Andrew Morton
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=1039123660.1433.12.camel@phantasy \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--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