From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org, linux-raid@vger.kernel.org,
Chris Mason <chris.mason@oracle.com>
Subject: Re: How to implement raid1 repair
Date: Thu, 17 Mar 2011 18:52:38 +0100 [thread overview]
Message-ID: <4D824A66.5020205@jan-o-sch.net> (raw)
In-Reply-To: <20110317171911.GA11704@dhcp231-156.rdu.redhat.com>
(snipped the parts already commented on in the other mails just sent)
On 03/17/2011 06:19 PM, Josef Bacik wrote:
> On Thu, Mar 17, 2011 at 03:46:43PM +0100, Jan Schmidt wrote:
>> If either of the answers is "no", tracking where the initial read came
>> from seems inevitable. Tracking would be very easy if bios came back
>> with unmodified values in bd_bdev and bd_sector, which is not the case.
>
> Huh? The bios come back with the bi_bdev/bi_sector they were submitted on, how
> are you getting something different? Thanks,
That's only if you write to the block device directly. If I'm not
mistaken, you'll have bi_bdev and bi_sector modified when using bios
with partitions to block-device-absolute values.
Jan
next prev parent reply other threads:[~2011-03-17 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:46 How to implement raid1 repair Jan Schmidt
2011-03-17 17:19 ` Josef Bacik
2011-03-17 17:52 ` Jan Schmidt [this message]
2011-03-17 17:36 ` Chris Mason
2011-03-17 17:49 ` Jan Schmidt
[not found] ` <AANLkTi=ckrr4BNSPxkMCveLAY7NyQ6SF6OzYHMnxC-rD@mail.gmail.com>
2011-03-17 17:37 ` Jan Schmidt
2011-03-17 17:42 ` Chris Mason
2011-03-17 17:45 ` Andrey Kuzmin
2011-03-17 17:45 ` Andrey Kuzmin
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=4D824A66.5020205@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--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 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.