linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Psalle <psalleetsile@gmail.com>
To: Mackenzie Meyer <snackmasterx@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS RAM requirements, RAID 6 stability/write holes and expansion questions
Date: Wed, 10 Feb 2016 11:16:00 +0100	[thread overview]
Message-ID: <56BB0DE0.5020102@gmail.com> (raw)
In-Reply-To: <CAKr9ZMFwxZ01gw7SAyFReOfXFb=hVzUXNgYoGcUc2xzLuo+9mg@mail.gmail.com>

On 05/02/16 20:36, Mackenzie Meyer wrote:
> RAID 6 stability?
I'll say more: currently, btrfs is in a state of flux where if you don't 
have a very recent kernel that's the first recommendation you're going 
to receive in case of problems. This means going out of stable packages 
in most distros.

Once you're in the bleeding kernel edge, you are obviously more likely 
to run into undiscovered bugs. I even see here people that has to patch 
the kernel with still non-mainline patches when trying to recover.

So don't for anything but testing.

      parent reply	other threads:[~2016-02-10 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 19:36 BTRFS RAM requirements, RAID 6 stability/write holes and expansion questions Mackenzie Meyer
2016-02-06  8:43 ` Duncan
2016-02-09 14:07 ` Psalle
2016-02-09 20:39 ` Chris Murphy
2016-02-10 13:57   ` Austin S. Hemmelgarn
2016-02-10 19:06     ` Chris Murphy
2016-02-10 19:59       ` Austin S. Hemmelgarn
2016-02-11 14:14         ` Goffredo Baroncelli
2016-02-11 14:58           ` Austin S. Hemmelgarn
2016-02-11 17:29             ` Chris Murphy
2016-02-10 10:16 ` Psalle [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=56BB0DE0.5020102@gmail.com \
    --to=psalleetsile@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=snackmasterx@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).