linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Ormanns <yann-ormanns@web.de>
To: lists@xunil.at
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Do I understand my RAID6 correctly?
Date: Tue, 12 Apr 2011 11:23:36 +0200	[thread overview]
Message-ID: <4DA41A18.9030602@web.de> (raw)
In-Reply-To: <4DA40FA4.80605@xunil.at>

Subject: Do I understand my RAID6 correctly?
From: Stefan G. Weichinger <lists@xunil.at>
To: Yann Ormanns <yann-ormanns@web.de>
Date: 2011-04-12 11:11 (+0200)

>      Array Size : 4391334912 (4187.90 GiB 4496.73 GB)
>   Used Dev Size : 731889152 (697.98 GiB 749.45 GB)
>    Raid Devices : 8
>   Total Devices : 9
> Preferred Minor : 3
>     Persistence : Superblock is persistent
> 
>  Active Devices : 8
> Working Devices : 8
>  Failed Devices : 1

You now have 9 devices in this Array (750GB*8 = 6 TB, 6 TB - (2*750GB) =
4.5 TB). One of them is the failed spare disk. That means, that this
array can "lose" two disks without losing data, as you already wrote.

Of course you can re-use /dev/sdk as a spare disk, but before, you
should check, why it failed (SMART data for example).

You should also have a look at the used drive models. E.g. if this array
uses 9x model XYZ from manucaturer ABC, perhaps more drives will fail in
the next time.
If the array uses mixed models, it should not be THAT urgent - but that
depends on the importance of the data...
I've read several times of people losing their RAID6, because they did
not mix the hard drive models. Then, a manufacturing fault have very bad
consequences.

Best regards,
Yann

  reply	other threads:[~2011-04-12  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12  8:39 Do I understand my RAID6 correctly? Stefan G. Weichinger
2011-04-12  9:23 ` Yann Ormanns [this message]
2011-04-12 10:42   ` Stefan G. Weichinger
2011-04-12 17:17     ` Yann Ormanns

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=4DA41A18.9030602@web.de \
    --to=yann-ormanns@web.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@xunil.at \
    /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).