All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Jan Vales <jan@jvales.net>, linux-btrfs@vger.kernel.org
Subject: Re: RAID56 status?
Date: Sun, 22 Jan 2017 23:35:49 +0100	[thread overview]
Message-ID: <1485124549.6187.36.camel@scientia.net> (raw)
In-Reply-To: <d69f5a19-baa8-ff56-609e-4ee01be8a103@jvales.net>

[-- Attachment #1: Type: text/plain, Size: 369 bytes --]

On Sun, 2017-01-22 at 22:22 +0100, Jan Vales wrote:
> Therefore my question: whats the status of raid5/6 is in btrfs?
> Is it somehow "production"-ready by now?
AFAIK, what's on the - apparently already no longer updated - 
https://btrfs.wiki.kernel.org/index.php/Status still applies, and
RAID56 is not yet usable for anything near production.

Cheers,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]

  reply	other threads:[~2017-01-22 22:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 21:22 RAID56 status? Jan Vales
2017-01-22 22:35 ` Christoph Anton Mitterer [this message]
2017-01-22 22:39   ` Hugo Mills
2017-01-22 22:48     ` Waxhead
2017-01-22 22:56     ` Christoph Anton Mitterer
2017-01-23  0:25     ` Jan Vales
2017-01-23  1:34       ` Qu Wenruo
     [not found]         ` <CALqCWCXNoKqAJR=7c4wzOvVjSBxNRMsUYMvkfRMcVk14dkp27Q@mail.gmail.com>
2017-01-23  5:24           ` Qu Wenruo
2017-01-23 17:53             ` Christoph Anton Mitterer
2017-01-23 23:18               ` Chris Mason
2017-01-23 23:31                 ` Christoph Anton Mitterer
2017-01-24 14:36                   ` Niccolò Belli
2017-01-23  6:57       ` Brendan Hide
2017-01-23  8:34         ` Janos Toth F.

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=1485124549.6187.36.camel@scientia.net \
    --to=calestyo@scientia.net \
    --cc=jan@jvales.net \
    --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.