Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Michael <mike@draftx.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: RAID 5/6
Date: Mon, 22 Oct 2012 17:05:00 +0100	[thread overview]
Message-ID: <20121022160500.GZ25498@carfax.org.uk> (raw)
In-Reply-To: <CAGJTRch_o4SDnT+n0WnUfRysj-9T-6GmvsUrSd6XiU6C2JoEsA@mail.gmail.com>

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

On Mon, Oct 22, 2012 at 10:58:07AM -0500, Michael wrote:
> Does anyone know when RAID 5/6 are planned to be included in the
> Kernel?

   This is in the FAQ:

https://btrfs.wiki.kernel.org/index.php/FAQ#Can_I_use_RAID.5B56.5D_on_my_Btrfs_filesystem.3F

   Short answer: Not yet, probably soon.

> I am starting to buy parts for my next computer and would very
> much like to use BTRFS because I want a FS that can grow and also
> recover from undetected read errors - it will be large enough that
> these are possible. I'm hoping that it will be available for use in
> the coming months.

   You can switch storage types on the fly, so you could at least
start with RAID-1, and then restripe to RAID-5 (or -6) when it's
stable enough for you. This assumes that you can manage to use RAID-1
in the first place and expand later.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
  --- "There's more than one way to do it" is not a commandment. It ---  
                           is a dire warning.                            

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-10-22 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 15:58 RAID 5/6 Michael
2012-10-22 16:05 ` Hugo Mills [this message]
2012-10-22 17:44   ` Andreas Philipp
2012-10-23 14:02     ` Michael

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=20121022160500.GZ25498@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mike@draftx.net \
    /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