From: "H. Peter Anvin" <hpa@zytor.com>
To: Gareth Pye <gareth@cerberos.id.au>
Cc: 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 15:37:29 -0700 [thread overview]
Message-ID: <4FE8E829.6060305@zytor.com> (raw)
In-Reply-To: <CA+WRLO87LvTrRJRMNwYQ3SwmZWF7WzO_FDi1=jqt1kwX=YSnWQ@mail.gmail.com>
On 06/25/2012 03:28 PM, Gareth Pye wrote:
> To me one doesn't have to be triggered, a user expects to have to tell
> the disks to rebuild/resync/balance after adding a disk, they may want
> to wait till they've added all 4 disks and run a few extra commands
> before they run the rebalance.
They do? E.g. mdadm doesn't make them...
> What is important is having a mode that
> doesn't require the user to remember that what they had used as the
> closest analogue to RAID1 that BTRFS supports requires them to run
> another command to change the 'RAID level' to be the RAID1 analogue for
> the new number of disks.
>
> Users will forget that and they will lose data because of it. At least
> with a M=N mode BTRFS can say they tried to make it easy to avoid that
> pitfall.
Doesn't that contradict your previous statement? In either case, I
agree with the latter...
-hpa
next prev parent reply other threads:[~2012-06-25 22:37 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 [this message]
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=4FE8E829.6060305@zytor.com \
--to=hpa@zytor.com \
--cc=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=gareth@cerberos.id.au \
--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.