From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid/device failure
Date: Mon, 11 Feb 2013 02:13:53 -0700 [thread overview]
Message-ID: <201302110213.53880.thomas@fjellstrom.ca> (raw)
In-Reply-To: <23314523.6.1360571363962.JavaMail.root@zimbra>
On February 11, 2013, Roy Sigurd Karlsbakk wrote:
> > I've re-configured my NAS box (still haven't put it into "production")
> > to be a
> > raid5 over 7 2TB consumer seagate barracuda drives, and with some
> > tweaking, performance was looking stellar.
>
> Using that many drives in raid-5 is a bit risky. Better use raid-6…
>
> Just my 2c
Yeah, I had first set it up in raid6. But I will have a separate backup array
of this array. Nothing fancy, just a linear concat of some 3TB+1TB disks,
though it may eventually get upgraded to a raid5 of 3TB disks.
I've figured that if I lose three disks all within the 5 hour time it takes to
do a full rebuild, I probably have larger problems to worry about than losing
my collection of random linux isos, even more random downloaded files, debian
apt mirror, one copy of my important backed up files, and miscelaneous media
files. I'll be running with the bitmap enabled, so if there are minor
problems, the array will take minutes to resync rather than hours.
Also, since I've gotten decent power supplies and UPSs, I haven't had very
many issues with harddrives. I personally haven't had a drive failure that
wasn't within the first couple weeks of purchase in years. And I always try to
make sure to stress test disks before putting them into service to weed out
SIDS.
This way I get the 10TB+ I was aiming for when I decided to build a NAS. In
raid6, I get 9.2TB or so. Very close I know ;)
> Vennlige hilsener / Best regards
>
> roy
> --
> Roy Sigurd Karlsbakk
> (+47) 98013356
> roy@karlsbakk.net
> http://blogg.karlsbakk.net/
> GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
> --
> I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det
> er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse
> av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer
> adekvate og relevante synonymer på norsk. --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Thomas Fjellstrom
thomas@fjellstrom.ca
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-02-11 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 1:27 raid/device failure Thomas Fjellstrom
2013-02-11 2:09 ` Phil Turmel
2013-02-11 2:52 ` EJ Vincent
2013-02-11 3:44 ` Phil Turmel
2013-02-11 20:28 ` EJ Vincent
2013-02-11 2:55 ` Thomas Fjellstrom
2013-02-11 3:22 ` Brad Campbell
2013-02-11 7:55 ` Thomas Fjellstrom
2013-02-11 8:29 ` Roy Sigurd Karlsbakk
2013-02-11 9:13 ` Thomas Fjellstrom [this message]
2013-02-12 22:31 ` Thomas Fjellstrom
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=201302110213.53880.thomas@fjellstrom.ca \
--to=thomas@fjellstrom.ca \
--cc=linux-raid@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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.