From: Paul Clements <paul.clements@steeleye.com>
To: neilb@cse.unsw.edu.au
Cc: linux-raid@vger.kernel.org
Subject: [BUG / PATCH] raid1: set BIO_UPTODATE after read error
Date: Fri, 10 Sep 2004 16:22:31 -0400 [thread overview]
Message-ID: <41420D07.4060001@steeleye.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
Neil,
unless you've already done so, I believe there is a little fix needed in
the raid1 read reschedule code. As the code currently works, a read that
is retried will continue to fail and cause raid1 to go into an infinite
retry loop:
Sep 10 14:42:04 fiji kernel: raid1: sdb1: redirecting sector 2 to
another mirror
Sep 10 14:42:04 fiji kernel: raid1: sdb1: rescheduling sector 2
Sep 10 14:42:04 fiji kernel: raid1: sdb1: redirecting sector 2 to
another mirror
Sep 10 14:42:04 fiji kernel: raid1: sdb1: rescheduling sector 2
Sep 10 14:42:04 fiji kernel: raid1: sdb1: redirecting sector 2 to
another mirror
Patch attached.
Thanks,
Paul
[-- Attachment #2: md_raid1_bio_uptodate_fix.diff --]
[-- Type: text/plain, Size: 439 bytes --]
--- linux/drivers/md/raid1.c.orig 2004-09-10 13:49:58.000000000 -0400
+++ linux/drivers/md/raid1.c 2004-09-10 15:46:47.000000000 -0400
@@ -970,6 +970,8 @@ static void raid1d(mddev_t *mddev)
bio->bi_bdev = rdev->bdev;
bio->bi_sector = r1_bio->sector + rdev->data_offset;
bio->bi_rw = READ;
+ /* clear any previous error */
+ set_bit(BIO_UPTODATE, &bio->bi_flags);
unplug = 1;
generic_make_request(bio);
}
next reply other threads:[~2004-09-10 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 20:22 Paul Clements [this message]
2004-09-13 5:32 ` [BUG / PATCH] raid1: set BIO_UPTODATE after read error Neil Brown
2004-09-15 17:34 ` Paul Clements
2004-09-16 10:50 ` Write and verify correct data to read-failed sectors before degrading array? Tim Small
2004-09-17 0:39 ` Neil Brown
2004-09-17 1:41 ` Sebastian Sobolewski
2004-09-17 2:00 ` Neil Brown
2004-09-17 2:13 ` Sebastian Sobolewski
2004-09-22 0:06 ` [PATCH] " Sebastian Sobolewski
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=41420D07.4060001@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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.