From: Andrew Morton <akpm@osdl.org>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2+ext3+dbench=Buffer I/O error
Date: Wed, 30 Jul 2003 15:09:02 -0700 [thread overview]
Message-ID: <20030730150902.5281f72c.akpm@osdl.org> (raw)
In-Reply-To: <5.2.1.1.2.20030730163933.00b41b50@wen-online.de>
Mike Galbraith <efault@gmx.de> wrote:
>
> Greetings,
>
> While trying to duplicate Randy Hron's "dbench has intermittent hang on
> 2.6.0-test1-ac2" report, I received quite a few "Buffer I/O error on
> /dev/hda8, logical block N" messages. (changing elevators makes no
> difference fwiw).
That's just a gremlinlet. You can delete the offending printk for now.
> I went back to test1, and it spat up a couple of "buffer
> layer error" messages and associated traces. Attempting to umount
> afterward to run fsck left umount in D state. See attachment.
Well that's a worry. Is it repeatable?
next prev parent reply other threads:[~2003-07-30 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 14:54 2.6.0-test2+ext3+dbench=Buffer I/O error Mike Galbraith
2003-07-30 22:09 ` Andrew Morton [this message]
2003-07-30 22:55 ` Lou Langholtz
2003-07-31 12:05 ` Jens Axboe
2003-07-31 4:13 ` Mike Galbraith
2003-07-31 16:54 ` Bill Davidsen
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=20030730150902.5281f72c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=efault@gmx.de \
--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