All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: "dave@thekilempire.com" <dave@thekilempire.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Status of raid5/6 in 2014?
Date: Sat, 4 Jan 2014 01:11:00 +0000	[thread overview]
Message-ID: <1388797899.23513.2.camel@ret.masoncoding.com> (raw)
In-Reply-To: <CAAVQaYAx8yxtvM1Mg759FJpEx6rjHQo3_2F84LNMA_f0kP81Sg@mail.gmail.com>

On Fri, 2014-01-03 at 11:45 -0500, Dave wrote:
> Back in Feb 2013 there was quite a bit of press about the preliminary
> raid5/6 implementation in Btrfs.  At the time it wasn't useful for
> anything other then testing and it's my understanding that this is
> still the case.
> 
> I've seen a few git commits and some chatter on this list but it would
> appear the developers are largely silent.  Parity based raid would be
> a powerful addition the the Btrfs feature stack and it's the feature I
> most anxiously await.  Are there any milestones planned for 2014?
> 
> Keep up the good work...

Thanks!  The big thing missing from RAID5/6 has been logging of parity
to make sure the parity is consistent after a power outage.  I'm back on
this now, and making some progress.

We also need to fix scrub support for raid5/6, which will happen after
the parity work.

-chris


      parent reply	other threads:[~2014-01-04  1:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 16:45 Status of raid5/6 in 2014? Dave
2014-01-04  1:04 ` Hans-Kristian Bakke
2014-01-04  1:11 ` Chris Mason [this message]

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=1388797899.23513.2.camel@ret.masoncoding.com \
    --to=clm@fb.com \
    --cc=dave@thekilempire.com \
    --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.