All of lore.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 14:52:39 -0700	[thread overview]
Message-ID: <20140324215239.GC11533@merlins.org> (raw)
In-Reply-To: <lgq0b9$e5r$1@ger.gmane.org>

On Mon, Mar 24, 2014 at 07:17:12PM +0000, Martin wrote:
> Thanks for the very good summary.
> 
> So... In very brief summary, btrfs raid5 is very much a work in progress.

If you know how to use it, which I didn't know do now, it's technically very
usable as is. The corner cases are in having a failing drive which you can't
hot remove because you can't write to it.
It's unfortunate that you can't just "kill" a drive without umounting,
making the drive disappear so that btrfs can't see it (dmsetup remove
cryptname for me, so it's easy to do remotely), and remounting in degraded
mode.
 
> Question: Is the raid5 going to be seamlessly part of the
> error-correcting raids whereby raid5, raid6,
> raid-with-n-redundant-drives are all coded as one configurable raid?

I'm not sure I parse your question. As far as btrfs is concerned you can
switch from non raid to raid5 to raid6 by adding a drive and rebalancing
which effectively reads and re-writes all the blocks in the new format.

> Also (second question): What happened to the raid naming scheme that
> better described the btrfs-style of raid by explicitly numbering the
> number of devices used for mirroring, striping, and error-correction?

btrfs fi show kind of tells you that if you know how to read it (I didn't
initially). What's missing for you?

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-24 21:52 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 [this message]
2014-03-25  1:11     ` Martin
2014-03-25  1:29       ` Marc MERLIN
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=20140324215239.GC11533@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 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.