public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brendan Hide <brendan@swiftspirit.co.za>
To: Duncan <1i5t5.duncan@cox.net>,
	linux-btrfs@vger.kernel.org, Hugo Mills <hugo@carfax.org.uk>,
	Russell Coker <russell@coker.com.au>
Subject: Re: copies= option
Date: Sun, 04 May 2014 09:27:10 +0200	[thread overview]
Message-ID: <5365EBCE.1060605@swiftspirit.co.za> (raw)
In-Reply-To: <pan$9bead$d5bbe620$2c7141f7$fab07860@cox.net>

On 2014/05/04 05:27 AM, Duncan wrote:
> Russell Coker posted on Sun, 04 May 2014 12:16:54 +1000 as excerpted:
>
>> Are there any plans for a feature like the ZFS copies= option?
>>
>> I'd like to be able to set copies= separately for data and metadata.  In
>> most cases RAID-1 provides adequate data protection but I'd like to have
>> RAID-1 and copies=2 for metadata so that if one disk dies and another
>> has some bad sectors during recovery I'm unlikely to lose metadata.
> Hugo's the guy with the better info on this one, but until he answers...
>
> The zfs license issues mean it's not an option for me and I'm thus not
> familiar with its options in any detail, but if I understand the question
> correctly, yes.
>
> And of course since btrfs treats data and metadata separately, it's
> extremely unlikely that any sort of copies= option wouldn't be separately
> configurable for each.
>
> There was a discussion of a very nice multi-way-configuration schema that
> I deliberately stayed out of as both a bit above my head and far enough
> in the future that I didn't want to get my hopes up too high about it
> yet.  I already want N-way-mirroring so bad I can taste it, and this was
> that and way more... if/when it ever actually gets coded and committed to
> the mainline kernel btrfs.  As I said, Hugo should have more on it, as he
> was active in that discussion as it seemed to line up perfectly with his
> area of interest.
>
The simple answer is yes, this is planned. As Duncan implied, however, 
it is not on the immediate roadmap. Internally we appear to be referring 
to this feature as "N-way redundancy" or "N-way mirroring".

My understanding is that the biggest hurdle before the primary devs will 
look into N-way redundancy is to finish the Raid5/6 implementation to 
include self-healing/scrubbing support - a critical issue before it can 
be adopted further.

-- 
__________
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97


  reply	other threads:[~2014-05-04  7:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04  2:16 copies= option Russell Coker
2014-05-04  3:27 ` Duncan
2014-05-04  7:27   ` Brendan Hide [this message]
     [not found]   ` <xjTK1n01B308YdQ01jTMAf>
2014-05-04 18:12     ` Duncan
2014-05-04 18:31       ` Hugo Mills
2014-05-05  2:59         ` Duncan
2014-05-06 20:13       ` Chris Murphy

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=5365EBCE.1060605@swiftspirit.co.za \
    --to=brendan@swiftspirit.co.za \
    --cc=1i5t5.duncan@cox.net \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell@coker.com.au \
    /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