From: Neil Conway <nconway.list@ukaea.org.uk>
To: reality@delusion.de, linux-kernel@vger.kernel.org
Subject: Re: Ext3 errors with 2.4.18
Date: Tue, 14 May 2002 11:59:02 +0100 [thread overview]
Message-ID: <3CE0EDF6.621AB9D0@ukaea.org.uk> (raw)
Your errors are just like the ones I experienced due to an IDE bug.
Are you:
a) using a hard-disk on the same cable as a CD/DVD
b) seeing any "hdX: status error: status=0x58 {DriveReady SeekComplete
DataRequest}" errors in your log
c) seeing (b) in close proximity to ATAPI module init messages like:
"hdb: ATAPI 24X DVD-ROM drive, 128kB Cache, UDMA(33)"
?
If yes to all/most of the above, you may be suffering from the same
bug. If not, your inodes in RAM are probably being trashed by a
different bug :-))
Neil
next reply other threads:[~2002-05-14 10:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 10:59 Neil Conway [this message]
2002-05-14 11:37 ` Ext3 errors with 2.4.18 Oliver Feiler
-- strict thread matches above, loose matches on Subject: below --
2002-05-06 16:25 Udo A. Steinberg
2002-05-06 17:20 ` Mike Fedyk
2002-05-06 17:32 ` Udo A. Steinberg
2002-05-06 21:11 ` Andrew Morton
2002-05-14 10:38 ` Oliver Feiler
2002-05-14 10:49 ` Andreas Dilger
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=3CE0EDF6.621AB9D0@ukaea.org.uk \
--to=nconway.list@ukaea.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=reality@delusion.de \
/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