linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <paul.clements@steeleye.com>
To: linux-raid@vger.kernel.org
Cc: Neil Brown <neilb@suse.de>
Subject: Re: [BUG] raid1: barrier retry does not work correctly with write-behind
Date: Thu, 03 Aug 2006 23:35:33 -0400	[thread overview]
Message-ID: <44D2C085.7010109@steeleye.com> (raw)
In-Reply-To: <44D2BA5A.3020809@steeleye.com>

Paul Clements wrote:

> I think bio_clone gives us that already. I may have missed something but 
> I think we have everything we need:
> 
> When a bio comes into raid1's make_request we bio_clone for each drive 
> and attach those to r1_bio->bios. We also have behind_pages, which 
> contains the pages. I think maybe instead of cloning r1_bio->master_bio, 
> we can just clone r1_bio->bios[i]. Does that make sense?

Never mind, of course that won't work...it's basically the same as using 
the failed bio.

Yes, so we need a copy of the bvec too. Would it be easier, or less 
risky just to create an entire "spare" bio, cloned from the master bio 
during make_request as the other r1_bio->bios[] are, and then use that 
if we need it? Maybe too much overhead, but it should guarantee that 
none of the fields have been monkey-ed with by an underlying disk. May 
be easier than trying to allocate and construct bvecs by hand?

--
Paul

      reply	other threads:[~2006-08-04  3:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 15:44 [BUG] raid1: barrier retry does not work correctly with write-behind Paul Clements
2006-08-04  1:47 ` Neil Brown
2006-08-04  3:09   ` Paul Clements
2006-08-04  3:35     ` Paul Clements [this message]

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=44D2C085.7010109@steeleye.com \
    --to=paul.clements@steeleye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).