From: Matt Mackall <mpm@selenic.com>
To: Sander van Malssen <svm@kozmix.org>,
Andrew Morton <akpm@osdl.org>,
yoh@onerussian.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-bk3 phantom I/O errors
Date: Sun, 3 Aug 2003 19:42:27 -0500 [thread overview]
Message-ID: <20030804004227.GZ22824@waste.org> (raw)
In-Reply-To: <20030803094634.GA430@kozmix.org>
On Sun, Aug 03, 2003 at 11:46:34AM +0200, Sander van Malssen wrote:
> On Sunday, 03 August 2003 at 02:17:27 -0700, Andrew Morton wrote:
>
> > Sander van Malssen <svm@kozmix.org> wrote:
> > >
> > > Well, that's funny. If I run a pristine test2-mm3-1 kernel I don't get
> > > those "Buffer I/O error on device ..." kernel messages anymore, but I do
> > > get the actual I/O error itself.
> >
> > The readahead problem got itself fixed. You are seeing something
> > unrelated.
> >
> > Please send a lot more details.
>
> Alas no interesting kernel messages to show. FS is an ext3 on an IDE
> disk, no initrd.
>
> The problem is easily reproduced thusly:
>
> root@ava:~ # cat /var/log/kozmix/brooksie.log > /dev/null
> cat: /var/log/kozmix/brooksie.log: Input/output error
> Linux version 2.6.0-test2-mm3 (svm@ava.kozmix.org) (gcc version 3.2.2) #4 Sun Aug 3 11:29:19 CEST 2003
Sure you've got mm3-1? Andrew didn't bump the EXTRAVERSION.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-08-04 0:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 15:31 2.6.0-test2-bk3 phantom I/O errors Yaroslav Halchenko
2003-07-29 20:50 ` Andrew Morton
2003-07-29 21:11 ` Yaroslav Halchenko
2003-07-30 17:04 ` Sander van Malssen
2003-07-30 17:23 ` Yaroslav Halchenko
2003-07-30 19:00 ` Andrew Morton
2003-07-30 19:11 ` Sander van Malssen
2003-08-03 9:10 ` Sander van Malssen
2003-08-03 9:17 ` Andrew Morton
2003-08-03 9:46 ` Sander van Malssen
2003-08-04 0:42 ` Matt Mackall [this message]
2003-08-04 10:59 ` Sander van Malssen
-- strict thread matches above, loose matches on Subject: below --
2003-07-27 19:10 Sander van Malssen
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=20030804004227.GZ22824@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=svm@kozmix.org \
--cc=yoh@onerussian.com \
/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;
as well as URLs for NNTP newsgroup(s).