From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Actual effect of mkfs.btrfs -m raid10 </dev/sdX> ... -d raid10 </dev/sdX> ...
Date: Wed, 20 Nov 2013 06:35:01 +0000 [thread overview]
Message-ID: <l6hl6b$i5h$1@ger.gmane.org> (raw)
In-Reply-To: <pan$cd41e$ced598aa$e5d2ed3a$3c71af6f@cox.net>
On 19/11/13 23:16, Duncan wrote:
> So we have:
>
> 1) raid1 is exactly two copies of data, paired devices.
>
> 2) raid0 is a stripe exactly two devices wide (reinforced by to read a
> stripe takes only two devices), so again paired devices.
Which is fine for some occasions and a very good start point.
However, I'm sure there is a strong wish to be able to specify n-copies
of data/metadata spread across m devices. Or even to specify 'hot spares'.
This would be a great to overcome the problem of a set of drives
becoming "read-only" when one btrfs drive fails or is removed.
(Or should we always mount with the "degraded" option?)
Regards,
Martin
next prev parent reply other threads:[~2013-11-20 6:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 5:12 Actual effect of mkfs.btrfs -m raid10 </dev/sdX> ... -d raid10 </dev/sdX> deadhorseconsulting
2013-11-19 9:06 ` Hugo Mills
2013-11-19 19:24 ` deadhorseconsulting
2013-11-19 21:04 ` Duncan
2013-11-20 6:41 ` Martin
2013-11-19 23:16 ` Duncan
2013-11-20 6:35 ` Martin [this message]
2013-11-20 10:16 ` Chris Murphy
2013-11-20 10:22 ` Russell Coker
2013-11-20 8:09 ` Hugo Mills
2013-11-20 16:43 ` Duncan
2013-11-20 16:52 ` Hugo Mills
2013-11-20 21:13 ` Duncan
2013-11-21 17:14 ` Jeff Mahoney
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='l6hl6b$i5h$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--cc=linux-btrfs@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.