mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Brown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: dan@debian.org, linux-kernel@vger.kernel.org, ext3-users@redhat.com
Subject: Re: ext3 badness in 2.6.0-test2
Date: Sat, 9 Aug 2003 10:39:43 +1000	[thread overview]
Message-ID: <16180.17103.360112.493943@gargle.gargle.HOWL> (raw)
In-Reply-To: message from Andrew Morton on Thursday August 7

On Thursday August 7, akpm@osdl.org wrote:
> Neil Brown <neilb@cse.unsw.edu.au> wrote:
> 
> > So I guess the finger points generally in the direction of raid5.
> > Now I've just got to figure if it is a bug in r5, or some assumption
> > that it makes that is no longer valid (I was briefly suspicious of
> > PF_READAHEAD which could have made a real mess of raid5, but that
> > wouldn't have this symptom)
> 
> The PF_READAHEAD things was a huge bug.  Make sure that it is fixed before
> proceeding.  Linus's tree has the fix.

I found it. It was read-ahead related, but nothing to do with
PF_READAHEAD.

With this patch, my test ran to completion instead of dying at about
th 20% mark.

NeilBrown

=================================================================
Disable raid5 handling of read-ahead

raid5 trys to honour RWA_MASK, but messes it up and can return bad data.
Just ignore RWA_MASK for now.


 ----------- Diffstat output ------------
 ./drivers/md/raid5.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff ./drivers/md/raid5.c~current~ ./drivers/md/raid5.c
--- ./drivers/md/raid5.c~current~	2003-08-08 14:37:00.000000000 +1000
+++ ./drivers/md/raid5.c	2003-08-08 14:37:19.000000000 +1000
@@ -1326,7 +1326,7 @@ static int make_request (request_queue_t
 			(unsigned long long)new_sector, 
 			(unsigned long long)logical_sector);
 
-		sh = get_active_stripe(conf, new_sector, pd_idx, (bi->bi_rw&RWA_MASK));
+		sh = get_active_stripe(conf, new_sector, pd_idx, 0/*(bi->bi_rw&RWA_MASK)*/);
 		if (sh) {
 
 			add_stripe_bio(sh, bi, dd_idx, (bi->bi_rw&RW_MASK));



  reply	other threads:[~2003-08-09  0:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 14:22 Daniel Jacobowitz
2003-08-04 20:22 ` Andrew Morton
2003-08-06  6:36   ` Neil Brown
2003-08-06  6:57     ` Andrew Morton
2003-08-06 20:18       ` md+ext3 " Frank van de Pol
2003-08-08  1:00       ` ext3 " Neil Brown
2003-08-08  1:16         ` Andrew Morton
2003-08-09  0:39           ` Neil Brown [this message]
2003-08-09  1:05             ` Mike Fedyk
2003-08-10 23:44               ` Neil Brown
2003-08-06  6:40 rwhron

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=16180.17103.360112.493943@gargle.gargle.HOWL \
    --to=neilb@cse.unsw.edu.au \
    --cc=akpm@osdl.org \
    --cc=dan@debian.org \
    --cc=ext3-users@redhat.com \
    --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

all inboxes | Powered by JetHome®