From: ptb@lab.it.uc3m.es (Peter T. Breuer)
To: linux-raid@vger.kernel.org
Subject: Re: Spares and partitioning huge disks
Date: Tue, 11 Jan 2005 12:34:58 +0100 [thread overview]
Message-ID: <28qcb2-15v.ln1@news.it.uc3m.es> (raw)
In-Reply-To: okuab2-u4c.ln1@news.it.uc3m.es
I'm looking for a natural way to rewrite failed read sectors on read1. ANy
ideas? There are several pitfalls to do with barriers in the different
raid threads.
My first crude idea was to put into raid1_end_request a
sync_request(mddev, r1_bio->sector, 0);
just before raid1_end_bio_io(r1_bio) is run on a succesful retried
read. But this supposes that nothing in sync_request will sleep (or
is that ok in end_request nowadays). If not possible inline I will
have to schedule it instead.
Another possibility is not to run raid1_end_bio_io just yet but instead
convert the r1_bio we just did ok into a SPECIAL and put it on the retry
queue and let the raid1 treat it (by running the WRITE half of a
READ-WRITE resync operation on it). I can modify raid1d to do the
users end_bio_io for us if needed. Or I can run
sync_request_write(mddev, r1_bio);
directly (somehow I get a shiver down my spine) from the end_request.
Ideas? Advice? Derision?
OK - so to be definite, what would be wrong with
r1_bio->cmd = SPECIAL;
reschedule_retry(r1_bio);
instead of
raid_end_bio_io(r1_bio);
in raid1_end_request? This should result in the raid1d thread doing a
write-half to all devices from the bio buffer taht we just filled with
a successful read. The question is when we get to ack the user on the
read. Maybe I should clone the bio.
Peter
next prev parent reply other threads:[~2005-01-11 11:34 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 14:16 Spares and partitioning huge disks maarten
2005-01-06 16:46 ` Guy
2005-01-06 17:08 ` maarten
2005-01-06 17:31 ` Guy
2005-01-06 18:18 ` maarten
[not found] ` <41DD83DA.9040609@h3c.com>
2005-01-06 19:42 ` maarten
2005-01-07 20:59 ` Mario Holbe
2005-01-07 21:57 ` Guy
2005-01-08 10:22 ` Mario Holbe
2005-01-08 12:19 ` maarten
2005-01-08 16:33 ` Guy
2005-01-08 16:58 ` maarten
2005-01-08 14:52 ` Frank van Maarseveen
2005-01-08 15:50 ` Mario Holbe
2005-01-08 16:32 ` Guy
2005-01-08 17:16 ` maarten
2005-01-08 18:55 ` Guy
2005-01-08 19:25 ` maarten
2005-01-08 20:33 ` Mario Holbe
2005-01-08 23:01 ` maarten
2005-01-09 10:10 ` Mario Holbe
2005-01-09 16:23 ` Guy
2005-01-09 16:36 ` Michael Tokarev
2005-01-09 17:52 ` Peter T. Breuer
2005-01-09 17:59 ` Michael Tokarev
2005-01-09 18:34 ` Peter T. Breuer
2005-01-09 20:28 ` Guy
2005-01-09 20:47 ` Peter T. Breuer
2005-01-10 7:19 ` Peter T. Breuer
2005-01-10 9:05 ` Guy
2005-01-10 9:38 ` Peter T. Breuer
2005-01-10 12:31 ` Peter T. Breuer
2005-01-10 13:19 ` Peter T. Breuer
2005-01-10 18:37 ` Peter T. Breuer
2005-01-11 11:34 ` Peter T. Breuer [this message]
2005-01-08 23:09 ` Guy
2005-01-09 0:56 ` maarten
2005-01-13 2:05 ` Neil Brown
2005-01-13 4:55 ` Guy
2005-01-13 9:27 ` Peter T. Breuer
2005-01-13 15:53 ` Guy
2005-01-13 17:16 ` Peter T. Breuer
2005-01-13 20:40 ` Guy
2005-01-13 23:32 ` Peter T. Breuer
2005-01-14 2:43 ` Guy
2005-01-08 16:49 ` maarten
2005-01-08 19:01 ` maarten
2005-01-10 16:34 ` maarten
2005-01-10 16:36 ` Gordon Henderson
2005-01-10 17:10 ` maarten
2005-01-16 16:19 ` 4 questions. Chieftec chassis case CA-01B, resync times, selecting ide driver module loading, raid5 :2 drives on same ide channel Mitchell Laks
2005-01-16 17:53 ` Gordon Henderson
2005-01-16 18:22 ` Maarten
2005-01-16 19:39 ` Guy
2005-01-16 20:55 ` Maarten
2005-01-16 21:58 ` Guy
2005-01-10 17:13 ` Spares and partitioning huge disks Guy
2005-01-10 17:35 ` hard disk re-locates bad block on read Guy
2005-01-11 14:34 ` Tom Coughlan
2005-01-11 22:43 ` Guy
2005-01-12 13:51 ` Tom Coughlan
2005-01-10 18:24 ` Spares and partitioning huge disks maarten
2005-01-10 20:09 ` Guy
2005-01-10 21:21 ` maarten
2005-01-11 1:04 ` maarten
2005-01-10 18:40 ` maarten
2005-01-10 19:41 ` Guy
2005-01-12 11:41 ` RAID-6 Gordon Henderson
2005-01-13 2:11 ` RAID-6 Neil Brown
2005-01-15 16:12 ` RAID-6 Gordon Henderson
2005-01-17 8:04 ` RAID-6 Turbo Fredriksson
2005-01-11 10:09 ` Spares and partitioning huge disks KELEMEN Peter
2005-01-09 19:33 ` Frank van Maarseveen
2005-01-09 21:26 ` maarten
2005-01-09 22:29 ` Frank van Maarseveen
2005-01-09 23:16 ` maarten
2005-01-10 8:15 ` Frank van Maarseveen
2005-01-14 17:29 ` Dieter Stueken
2005-01-14 17:46 ` maarten
2005-01-14 19:14 ` Derek Piper
2005-01-15 0:13 ` Michael Tokarev
2005-01-15 9:34 ` Peter T. Breuer
2005-01-15 9:54 ` Mikael Abrahamsson
2005-01-15 10:31 ` Brad Campbell
2005-01-15 11:10 ` Mikael Abrahamsson
2005-01-15 10:33 ` Peter T. Breuer
2005-01-15 11:07 ` Mikael Abrahamsson
2005-01-09 23:20 ` Guy
2005-01-10 7:42 ` Gordon Henderson
2005-01-10 9:03 ` Guy
2005-01-10 12:21 ` Stats... [RE: Spares and partitioning huge disks] Gordon Henderson
2005-01-10 0:42 ` Spares and partitioning huge disks Guy
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 9:53 Bene Martin
2005-01-13 10:11 ` Peter T. Breuer
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=28qcb2-15v.ln1@news.it.uc3m.es \
--to=ptb@lab.it.uc3m.es \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).