linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Bouton <lionel-subscription@bouton.name>
To: Donald Pearson <donaldwhpearson@gmail.com>
Cc: Sjoerd <sjoerd@sjomar.eu>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: RAID6 stable enough for production?
Date: Wed, 14 Oct 2015 23:16:48 +0200	[thread overview]
Message-ID: <561EC640.1060106@bouton.name> (raw)
In-Reply-To: <CAC=t97COVc4kQ+A-jSVr3ujGb-0WGNh2qCcohBvLFw=YtnObhA@mail.gmail.com>

Le 14/10/2015 22:53, Donald Pearson a écrit :
> I've used it from 3.8 something to current, it does not handle drive
> failure well at all, which is the point of parity raid. I had a 10disk
> Raid6 array on 4.1.1 and a drive failure put the filesystem in an
> irrecoverable state.  Scrub speeds are also an order of magnitude or
> more slower in my own experience.  The issue isn't filesystem
> read/write performance, it's maintenance and operation.

Thanks, I'll proceed with caution...
When 3.19 got out I tried various tests with loopback devices in RAID6
(dd if=/dev/random in the middle of one loopback device guaranteed to
have file data while using the filesystem for example) and didn't manage
to break it but it was arguably simple situations (either missing device
or corrupted data on device, not something behaving really erratically
like failing hardware).

Lionel

  parent reply	other threads:[~2015-10-14 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 20:19 RAID6 stable enough for production? Sjoerd
2015-10-14 20:23 ` Donald Pearson
2015-10-14 20:34   ` Lionel Bouton
2015-10-14 20:53     ` Donald Pearson
2015-10-14 21:15       ` Rich Freeman
2015-10-14 21:19         ` Donald Pearson
2015-10-15  1:47         ` Chris Murphy
2015-10-15 16:40           ` Rich Freeman
2015-10-15 19:04             ` Chris Murphy
2015-10-14 21:16       ` Lionel Bouton [this message]
2015-10-15  1:55 ` Duncan

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=561EC640.1060106@bouton.name \
    --to=lionel-subscription@bouton.name \
    --cc=donaldwhpearson@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sjoerd@sjomar.eu \
    /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).