All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "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 11:21:42 -0400	[thread overview]
Message-ID: <20120625152142.GD17638@shiny> (raw)
In-Reply-To: <670f2f56-9918-4463-ad89-780ba80bfecc@email.android.com>

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

On Wed, Jun 20, 2012 at 07:34:27PM -0600, H. Peter Anvin wrote:
> Could you have a mode, though, where M = N at all times, so a user doesn't end up adding a new drive and get a nasty surprise?
> 
> Chris Mason <chris.mason@fusionio.com> wrote:
> 
> >On Wed, Jun 20, 2012 at 06:35:30PM -0600, Marios Titas wrote:
> >> On Wed, Jun 20, 2012 at 12:27 PM, H. Peter Anvin <hpa@zytor.com>
> >wrote:
> >> > Yet another boot loader support request.
> >> >
> >> > Right now btrfs' definition of "RAID-1" with more than two devices
> >is a
> >> > bit unorthodox: it stores on any two drives.  "True RAID-1" would
> >> > instead store N copies on each of N devices, the same way an actual
> >> > RAID-1 would operate with an arbitrary number of devices.
> >> >
> >> > This means that a bootloader can consider a single device in
> >isolation:
> >> > if the firmware gives access only to a single device, it can be
> >booted.
> >> >  Since /boot is usually a very small amount of data, this is a very
> >> > reasonable tradeoff.
> >> 
> >> +1
> >> 
> >> In fact, the current RAID-1 should not have been called RAID-1 at
> >all,
> >> it is confusing.
> >
> >With the raid5/6 code, I'm changing raid1 (and raid10) to have a
> >configurable number of copies.  So, you'll be able to have N copies on
> >M
> >drives, where N <= M.
> >
> >-chris
> 
> -- 
> Sent from my mobile phone. Please excuse brevity and lack of formatting.

  reply	other threads:[~2012-06-25 15:21 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 [this message]
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
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=20120625152142.GD17638@shiny \
    --to=chris.mason@fusionio.com \
    --cc=clmason@fusionio.com \
    --cc=hpa@zytor.com \
    --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 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.