From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Paul Loewenstein <paul.loewenstein@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Self-destruct of btrfs RAID6 array
Date: Fri, 20 Nov 2015 08:29:43 -0500 [thread overview]
Message-ID: <564F2047.5010508@gmail.com> (raw)
In-Reply-To: <564E9D62.4050306@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On 2015-11-19 23:11, Paul Loewenstein wrote:
> I have just had an apparently catastrophic collapse of a large RAID6
> array. I was hoping that the dual-redundancy of a RAID6 array would
> compensate for having no backup media large enough to back it up!
Duncan already did a really good job of explaining this (and from what I
can tell, I'm pretty sure his analysis of what's going on is correct),
but I would like to add a couple of things.
First, RAID is not a backup, it's a way to minimize the need to restore
from backups in the event of hardware failure (or, in the case of BTRFS,
also a way to minimize the effects of data corruption).
Second, have you considered doing encrypted backups to a cloud storage
service? This is what I personally do, and it works really well for me.
Amazon S3 has pretty reasonable pricing, and there are multiple
options on Linux to allow accessing it like a filesystem. There are
many other options as well (in my case, I backup to both S3 and Dropbox,
but I also have small enough backups that I don't need to worry about
the 1T limit on Dropbox for non-business accounts).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
prev parent reply other threads:[~2015-11-20 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 4:11 Self-destruct of btrfs RAID6 array Paul Loewenstein
2015-11-20 6:19 ` Duncan
2015-11-20 13:29 ` Austin S Hemmelgarn [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=564F2047.5010508@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=paul.loewenstein@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