From: Brad Campbell <lists2009@fnarfbargle.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: question about the best suited RAID level/layout
Date: Sun, 07 Jul 2013 14:36:10 +0800 [thread overview]
Message-ID: <51D90C5A.20308@fnarfbargle.com> (raw)
In-Reply-To: <1373122142.5217.7.camel@fermat.scientia.net>
On 06/07/13 22:49, Christoph Anton Mitterer wrote:
> On Sat, 2013-07-06 at 13:29 +0800, Brad Campbell wrote:
>> A messy process to be sure, but no risk of data loss that way.
> Sure... but that might not always be possible at all... imagine you're
> hit by a power outage (okay one could argue, that one must run an
> UPS)... or kernel panic...
If you are not running a UPS, you are not actually serious about your
data integrity. I don't care if its an APC BackUPS with 5 minutes
hold-up, you need to be able to shut down cleanly.
> Or people being very paranoid (like me) probably won't let their
> dm-crypt encrypted devices run when being away (freeze attacks against
> the RAM)...
I use dm-crypt too, but there are far easier ways to get access to my
data than performing a cold attack against my server, so I spend my
effort against those risks instead.
I guess if your risk assessment states that is a risk worthy of
mitigating then you have to do what you have to do. Paranoia for
paranoia's sake can be fun if you don't have anything else to do, but
unless there is a real (not perceived) risk, then you just balance your
treatments against that.
> Anyway... I guess this goes off topic ;)
>
Far, far, far...
> But I see that you have not real point *against* running devices from
> different vendors either. Correct me if I'm wrong ;)
Nope. Not wrong at all. That'd be my preference if practical. On the
other hand, my 10 x WD 2TB green drive RAID-6 is about the worst
potential time bomb, but then it's all backed up and restore-able if the
worst should happen. Risk is "very likely", consequence is minimal.
My work data on the other hand is on a RAID-10 of SAS drives with 60
days of rotating off site & off line backups. Risk is "unlikely", but
consequence is massive.
We had a TV advertising campaign targeting speeding here here for a few
years. To paraphrase : "Choose your speed(risk), choose your
consequences...".
next prev parent reply other threads:[~2013-07-07 6:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 18:17 question about the best suited RAID level/layout Christoph Anton Mitterer
2013-07-04 21:43 ` Phil Turmel
2013-07-04 22:58 ` Christoph Anton Mitterer
2013-07-05 1:07 ` Brad Campbell
2013-07-06 0:36 ` Christoph Anton Mitterer
2013-07-06 5:29 ` Brad Campbell
2013-07-06 14:49 ` Christoph Anton Mitterer
2013-07-07 6:36 ` Brad Campbell [this message]
2013-07-06 7:40 ` Piergiorgio Sartor
2013-07-06 14:52 ` Christoph Anton Mitterer
2013-07-05 1:12 ` Stan Hoeppner
2013-07-06 0:46 ` Christoph Anton Mitterer
2013-07-06 8:36 ` Stan Hoeppner
2013-07-06 15:04 ` Christoph Anton Mitterer
2013-07-06 15:41 ` Matt Garman
2013-07-07 14:08 ` David Brown
2013-07-07 16:45 ` Stan Hoeppner
2013-07-07 17:26 ` Christoph Anton Mitterer
2013-07-09 15:50 ` Stan Hoeppner
2013-07-05 13:36 ` Phil Turmel
2013-07-06 1:11 ` Christoph Anton Mitterer
2013-07-06 2:19 ` Phil Turmel
2013-07-06 17:55 ` Christoph Anton Mitterer
2013-07-07 12:46 ` Bernd Schubert
2013-07-07 17:39 ` Christoph Anton Mitterer
2013-07-05 11:10 ` David Brown
2013-07-06 0:55 ` Christoph Anton Mitterer
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=51D90C5A.20308@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=calestyo@scientia.net \
--cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.