linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Hugo Mills <hugo@carfax.org.uk>,
	Chris Mason <chris.mason@fusionio.com>,
	"Chris L. Mason" <clmason@fusionio.com>,
	Marios Titas <redneb8888@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Feature request: true RAID-1 mode
Date: Mon, 25 Jun 2012 16:00:49 -0700	[thread overview]
Message-ID: <4FE8EDA1.5090004@zytor.com> (raw)
In-Reply-To: <20120625225424.GG25572@carfax.org.uk>

On 06/25/2012 03:54 PM, Hugo Mills wrote:
> On Mon, Jun 25, 2012 at 10:46:01AM -0700, H. Peter Anvin wrote:
>> On 06/25/2012 08:21 AM, Chris Mason wrote:
>>> Yes and no.  If you have 2 drives and you add one more, we can
>>> make it do all new chunks over 3 drives.  But, turning the
>>> existing double mirror chunks into a triple mirror requires a
>>> balance.
>>> 
>>> -chris
>> 
>> So trigger one.  This is the exact analogue to the resync pass
>> that is required in classic RAID after adding new media.
> 
> You'd have to cancel and restart if a second new disk was added 
> while the first balance was ongoing. Fortunately, this isn't a
> problem these days.
> 
> Also, it occurs to me that I should just check -- are you aware 
> that the btrfs implementation of RAID-1 makes no guarantees about
> the location of any given piece of data? i.e. if I have a piece of
> data stored at block X on disk 1, it's not guaranteed to be stored
> at block X on disks 2, 3, 4, ... I'm not sure if this is important
> to you, but it's a significant difference between the btrfs
> implementation of RAID-1 and the MD implementation.
> 

I am aware of that, and it is not a problem... the one-device
bootloader can find out *which* disk it is talking to by comparing
uuids, and the btrfs data structures will tell it how to find the data
on that specific disk.  It does of course mean the bootloader needs to
be aware of the multidisk nature of btrfs, but that isn't a problem in
itself.

	-hpa


  reply	other threads:[~2012-06-25 23:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 16:27 Feature request: true RAID-1 mode H. Peter Anvin
2012-06-21  0:35 ` Marios Titas
2012-06-21  0:50   ` Chris Mason
2012-06-21  1:34     ` H. Peter Anvin
2012-06-25 15:21       ` Chris Mason
2012-06-25 17:46         ` H. Peter Anvin
2012-06-25 22:34           ` Gareth Pye
     [not found]           ` <CA+WRLO87LvTrRJRMNwYQ3SwmZWF7WzO_FDi1=jqt1kwX=YSnWQ@mail.gmail.com>
2012-06-25 22:37             ` H. Peter Anvin
2012-06-25 22:46               ` Gareth Pye
2012-06-25 22:54           ` Hugo Mills
2012-06-25 23:00             ` H. Peter Anvin [this message]
2012-07-02 15:59               ` H. Peter Anvin

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=4FE8EDA1.5090004@zytor.com \
    --to=hpa@zytor.com \
    --cc=chris.mason@fusionio.com \
    --cc=clmason@fusionio.com \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=redneb8888@gmail.com \
    /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).