From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Scrubbing with BTRFS Raid 5
Date: Wed, 22 Jan 2014 16:02:47 +0000 (UTC) [thread overview]
Message-ID: <pan$8caeb$d0be9e00$b714cdaf$5ed18e96@cox.net> (raw)
In-Reply-To: 52DEABC9.2040205@jrs-s.net
Jim Salter posted on Tue, 21 Jan 2014 12:18:01 -0500 as excerpted:
> Would it be reasonably accurate to say "btrfs' RAID5 implementation is
> likely working well enough and safe enough if you are backing up
> regularly and are willing and able to restore from backup if necessary
> if a device failure goes horribly wrong", then?
I'd say (and IIRC I did say somewhere, but don't remember if it was this
thread) that in reliability terms btrfs raid5 should be treated like
btrfs raid0 at this point. Raid0 is well known to have absolutely no
failover -- if a device fails, the raid is toast. It's possible so-
called "extreme measures" may recover data from the surviving bits (think
the $expen$ive$ $ervice$ of data recovery firms), but the idea is that
either no data that's not easily replaced is stored on a raid0 in the
first place, or if it is, there's (tested recoverable) backup to the
level that you're fully comfortable with losing EVERYTHING not backed up.
Examples of good data for raid0 are the kernel sources (as a user, not a
dev, so you're not hacking on them), your distro's local package cache,
browser cache, etc. This because by definition all those examples have
the net as their backup, so loss of a local copy means a bit more to
download, at worst.
That's what btrfs raid5/6 are at the moment, effectively raid0 from a
recovery perspective.
Now the parity /is/ being written; it simply can't be treated as
available for recovery. So supposing you do /not/ lose a device (or
suffer a bad checksum) on the raid5 until after the recovery code is
complete and available, you've effectively "free" upgraded from raid0
reliability to raid5 reliability as soon as recovery is possible, which
will be nice, and meanwhile you can test the operational functionality,
so there /are/ reasons you might want to run the btrfs raid5 mode now.
As long as you remember it's currently effectively raid0 should something
go wrong, and you either don't use it for valuable data in the first
place, or you're willing to do without any updates to that data since the
last tested backup, should it come to that.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-01-22 16:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 9:06 Scrubbing with BTRFS Raid 5 Graham Fleming
2014-01-21 17:08 ` Duncan
2014-01-21 17:18 ` Jim Salter
2014-01-21 17:38 ` Chris Murphy
2014-01-21 18:25 ` Jim Salter
2014-01-22 16:02 ` Duncan [this message]
2014-01-22 20:45 ` Chris Mason
2014-01-22 21:06 ` ronnie sahlberg
2014-01-22 21:16 ` Chris Mason
2014-01-22 22:36 ` ronnie sahlberg
-- strict thread matches above, loose matches on Subject: below --
2014-01-21 18:03 Graham Fleming
2014-01-22 15:39 ` Duncan
2014-01-20 0:53 Graham Fleming
2014-01-20 13:21 ` 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='pan$8caeb$d0be9e00$b714cdaf$5ed18e96@cox.net' \
--to=1i5t5.duncan@cox.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