From: Andrew Morton <akpm@osdl.org>
To: Sander van Malssen <svm@kozmix.org>
Cc: yoh@onerussian.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-bk3 phantom I/O errors
Date: Wed, 30 Jul 2003 12:00:02 -0700 [thread overview]
Message-ID: <20030730120002.29c13b0c.akpm@osdl.org> (raw)
In-Reply-To: <20030730170432.GA692@kozmix.org>
Sander van Malssen <svm@kozmix.org> wrote:
>
> If I try this on 2.6.0-test2-mm1 with the dump_stack() added (ext3, no
> initrd) I get the following:
>
>
> Buffer I/O error on device hda1, logical block 25361
> Call Trace:
> [<c0150f02>] buffer_io_error+0x42/0x50
OK, looks like the new readahead stuff confused the error reporting.
Does this make the error messages go away?
diff -puN mm/readahead.c~a mm/readahead.c
--- 25/mm/readahead.c~a 2003-07-30 11:58:07.000000000 -0700
+++ 25-akpm/mm/readahead.c 2003-07-30 11:58:20.000000000 -0700
@@ -96,7 +96,7 @@ static int read_pages(struct address_spa
struct pagevec lru_pvec;
int ret = 0;
- current->flags |= PF_READAHEAD;
+// current->flags |= PF_READAHEAD;
if (mapping->a_ops->readpages) {
ret = mapping->a_ops->readpages(filp, mapping, pages, nr_pages);
_
Tell me how hard this is to hit. Does it only happen when there is a large
amount of IO happening? What is the system doing at the time?
next prev parent reply other threads:[~2003-07-30 18:59 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 [this message]
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
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=20030730120002.29c13b0c.akpm@osdl.org \
--to=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 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.