linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Anderson <david.anderson@calixo.net>
To: linux-raid@vger.kernel.org
Cc: berk walker <berk.walker@verizon.net>
Subject: Re: I'm about ready to do SW-Raid5 - pointers needed
Date: Tue, 28 Oct 2003 01:37:26 +0100	[thread overview]
Message-ID: <3F9DBA46.7020806@calixo.net> (raw)
In-Reply-To: <3F9DAD4C.3000002@verizon.net>

Hi there.

First of all, as a satisfied swraid5 user for some time, I would like to 
point out someting: data loss is not just about the redundancy of a raid 
array. If you bought your disks from a faulty batch and they all die, 
you're still hosed. Raid is absolutely no excuse for not backing up data.

Now, on to the questions ;)

> is there an advantage to >more< than 1 spare drive?

If several disks die _in a row_. ie one dies, a spare is synced, a 
second dies after the sync. A fairly rare occurence I reckon (in my 
experience, multiple failures come in flocks, not in rows). And if it 
does happen, you'll have a little degraded mode time while you add a 
clean disk and add it to the array. No big deal _if_ you have an 
efficient backup routine.

> .. more than 3 drives in mdx?

Depends on how many you have, and how much failure you want your array 
to tolerate. The more you add disks, the more your array becomes 
intolerant to failure (more active disks means more potential failure 
points, but the threshold of 1 failed disk only remains). But you "lose" 
less space to parity.
In short, if you can afford it, stick to 3-disk raid5 with a few spares.

> why not cp old boot/root/whatever drive to mdx after 
> booting on floppy?

I wasn't aware of anything against that... When I got hold of higher 
capacity disks I created a new larger raid5 array and copied the old to 
the new (not a raw copy of course, a copy at the file system level).
But then again, my array was for a special mountpoint (/var/data), so I 
could mount it readonly and copy it. Maybe the warnings against copying 
/ were because of the write issue which could leave you with an 
inconsistent copy?

> is there an advantage to having various mdx's allocated to various 
> /directories?..ie: /home, var, /etc

I don't see any myself. The only advantage would be less data loss in 
the event of a failure, but since you backup on a regular basis, a 
catastrophic failure shouldn't bring you down too long anyway.

A final reminder: Have efficient backup routines!! Raid will help you 
prevent disasters, but when a disaster does occur (not if, when), you'll 
need fast recovery with minimal loss.

David Anderson

PS: did I tell you about the importance of backups? ;)



  reply	other threads:[~2003-10-28  0:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 23:42 I'm about ready to do SW-Raid5 - pointers needed berk walker
2003-10-28  0:37 ` David Anderson [this message]
2003-10-28  1:55   ` maarten van den Berg
2003-10-28  3:32     ` rob
2003-10-28  5:37     ` Luke Rosenthal
2003-10-28  8:20       ` Spinning down disks [Re: I'm about ready to do SW-Raid5 - pointers needed] Gordon Henderson
2003-10-28  8:39       ` I'm about ready to do SW-Raid5 - pointers needed Hermann Himmelbauer
2003-10-28  1:07 ` maarten van den Berg
2003-10-28  1:21   ` David Anderson
2003-10-28  1:35     ` maarten van den Berg
2003-10-28  1:55       ` David Anderson
2003-10-28  1:58       ` David Anderson
2003-10-28  8:23 ` Hermann Himmelbauer
2003-10-28  8:26 ` Gordon Henderson
2003-10-28 14:06   ` maarten van den Berg
2003-10-28 14:25     ` Gordon Henderson
2003-10-28 15:05       ` maarten van den Berg
2003-10-28 15:10         ` Gordon Henderson
2003-10-28 16:37         ` Norman Schmidt
2003-10-28 16:54           ` Gordon Henderson
2003-10-28 18:28     ` jlewis
2003-10-28 19:14       ` Gordon Henderson
2003-10-29  4:33         ` Maurice Hilarius
2003-10-28 19:51       ` maarten van den Berg

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=3F9DBA46.7020806@calixo.net \
    --to=david.anderson@calixo.net \
    --cc=berk.walker@verizon.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 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).