public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Martin <m_btrfs@ml1.co.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs and raid5 status with kernel 3.14, documentation, and howto
Date: Mon, 24 Mar 2014 18:29:16 -0700	[thread overview]
Message-ID: <20140325012916.GF11533@merlins.org> (raw)
In-Reply-To: <lgql40$lm5$1@ger.gmane.org>

On Tue, Mar 25, 2014 at 01:11:43AM +0000, Martin wrote:
> Yes, looking good, but for my usage I need the option to run ok with a
> failed drive. So, that's one to keep a development eye on for continued
> progress...
 
So it does run with a failed drive, it'll just fill the logs with write
errors, but continue working ok.
 
> There's a big thread a short while ago about using parity across
> n-devices where the parity is spread such that you can have 1, 2, and up
> to 6 redundant devices. Well beyond just raid5 and raid6:
> 
> http://lwn.net/Articles/579034/
 
Aah, ok. I didn't understand you meant that. I know nothing about that, but
to be honest, raid6 feels like it's enough for me :)

> btrfs raid1 at present is always just the two copies of data spread
> across whatever number of disks you have. A more flexible arrangement is
> to be able to set to have say 3 copies of data and use say 4 disks.
> There's a new naming scheme proposed somewhere that enumerates all the
> permutations possible for numbers of devices, copies and parity that
> btrfs can support. For me, that is a 'killer' feature beyond what can be
> done with md-raid for example.
 
Right. That's on the roadmap from what I read here, just not ready yet.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

  reply	other threads:[~2014-03-25  1:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23 22:56 Btrfs and raid5 status with kernel 3.14, documentation, and howto Marc MERLIN
2014-03-24 19:17 ` Martin
2014-03-24 21:52   ` Marc MERLIN
2014-03-25  1:11     ` Martin
2014-03-25  1:29       ` Marc MERLIN [this message]
2014-03-25  8:04         ` Brendan Hide

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=20140325012916.GF11533@merlins.org \
    --to=marc@merlins.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=m_btrfs@ml1.co.uk \
    /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