From: Jens Axboe <axboe@suse.de>
To: Lou Langholtz <ldl@aros.net>
Cc: Andrew Morton <akpm@osdl.org>, Mike Galbraith <efault@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2+ext3+dbench=Buffer I/O error
Date: Thu, 31 Jul 2003 14:05:12 +0200 [thread overview]
Message-ID: <20030731120512.GQ22104@suse.de> (raw)
In-Reply-To: <3F284CE6.6080701@aros.net>
On Wed, Jul 30 2003, Lou Langholtz wrote:
> Andrew Morton wrote:
>
> >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? . . .
> >
> Any chance this problem is a consequence of not yet having Sean
> Estabrooks partial bvec patch in this person's kernel???
> <http://www.ussg.iu.edu/hypermail/linux/kernel/0307.3/0861.html>. Jens
> said he applied it on 2003/7/27 so it doesn't seem like this could have
> made it into 2.6.0-test1-ac2.
no not unless Mike is using taskfile + pio, and even then I've never
heard of it triggering.
--
Jens Axboe
next prev parent reply other threads:[~2003-07-31 12:05 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
2003-07-30 22:55 ` Lou Langholtz
2003-07-31 12:05 ` Jens Axboe [this message]
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=20030731120512.GQ22104@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=ldl@aros.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.