From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: raid5/6 production use status?
Date: Thu, 02 Jun 2016 00:25:34 +0200 [thread overview]
Message-ID: <1464819934.6742.71.camel@scientia.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Hey.
I've lost a bit track recently and the wiki changelog doesn't seem to
contain much about how things went on at the RAID5/6 front... so how're
things going?
Is it already more or less "productively" usable? What's still missing?
I guess there still aren't any administrative tools that e.g. monitor
for failed disks or block errors?
Does that RAID5/6 itself work already? Is it possible to replace broken
devices (or such with block errors)? Are things like a completely
failing disk (during fs being online) handled gracefully?
How about scrubbing/repairing... I assume on read it would identify
silent block errors by the checksum[0] and rebuild it if possible,
doing what when it fails? Just giving read errors? Marking the btrfs
RAID failed and remounting the fs read-only?
Cheers & thx,
Chris.
[0] Except of course for the nodatacow case, which, albeit a major
case, unfortunately still seems to lack the important checksumming
support :-(
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next reply other threads:[~2016-06-01 22:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 22:25 Christoph Anton Mitterer [this message]
2016-06-02 9:24 ` raid5/6 production use status? Gerald Hopf
2016-06-02 9:35 ` Hugo Mills
2016-06-02 10:03 ` Gerald Hopf
2016-06-03 17:38 ` btrfs (was: raid5/6) production use status (and future)? Christoph Anton Mitterer
2016-06-03 19:50 ` btrfs Austin S Hemmelgarn
2016-06-04 1:51 ` btrfs Christoph Anton Mitterer
2016-06-04 7:24 ` btrfs Andrei Borzenkov
2016-06-04 17:00 ` btrfs Chris Murphy
2016-06-04 17:37 ` btrfs Christoph Anton Mitterer
2016-06-04 19:13 ` btrfs Chris Murphy
2016-06-04 22:43 ` btrfs Christoph Anton Mitterer
2016-06-05 15:51 ` btrfs Chris Murphy
2016-06-05 20:39 ` btrfs Christoph Anton Mitterer
2016-06-04 21:18 ` btrfs Andrei Borzenkov
2016-06-05 20:39 ` btrfs Henk Slager
2016-06-05 20:56 ` btrfs Christoph Anton Mitterer
2016-06-05 21:07 ` btrfs Hugo Mills
2016-06-05 21:31 ` btrfs Christoph Anton Mitterer
2016-06-05 23:39 ` btrfs Chris Murphy
2016-06-08 6:13 ` btrfs Duncan
2016-06-06 0:56 ` btrfs Chris Murphy
2016-06-06 13:04 ` btrfs Austin S. Hemmelgarn
[not found] ` <f4a9ef2f-99a8-bcc4-5a8f-b022914980f0@swiftspirit.co.za>
2016-06-04 2:13 ` btrfs Christoph Anton Mitterer
2016-06-04 2:36 ` btrfs Chris Murphy
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=1464819934.6742.71.camel@scientia.net \
--to=calestyo@scientia.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 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).