linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: RAID6 questions
Date: Fri, 3 Jul 2009 08:40:03 +0200	[thread overview]
Message-ID: <20090703064003.GC23464@maude.comedia.it> (raw)
In-Reply-To: <2bdd5a4c0907020822s7d136681g23a4e34e13f0be8@mail.gmail.com>

On Thu, Jul 02, 2009 at 05:22:54PM +0200, Marek wrote:
>5. In case one decides for a partitioned approach - does mdadm kick
>out faulty partitions or whole drives? I have read several sources
>including some comments on slashdot that it's much better to split
>large drives into many small partitions, but noone clarified in
maybe because those suggesting this are not able to come up with a
reasonable explanation?
>detail.  A possible though unlikely scenario would be simultaneous
>failure of all hdds in the array:
>
> md1 RAID6 sda1[_] sdb1[_] sdc1[U] sdd1[U] sde1[U] sdf1[U]
> md2 RAID6 sda2[U] sdb2[_] sdc2[_] sdd2[U] sde2[U] sdf2[U]
> md3 RAID6 sda3[U] sdb3[U] sdc3[_] sdd3[_] sde3[U] sdf3[U]
> md4 RAID6 sda4[U] sdb4[U] sdc4[U] sdd4[_] sde4[_] sdf4[U]
> md5 RAID6 sda5[U] sdb5[U] sdc5[U] sdd5[U] sde5[_] sdf5[_]
>(...)
>
>If mdadm kicks out faulty partitions only, but leaves the remaining
>part of drive going as long as it's able to read it, would it mean
>that even if every single hdd in the array failed somewhere (for
>example due to Reallocated_Sector_Ct), mdadm would keep the healthy
>partitions of that failed drive running, thus the entire system would
>be still running in degraded mode without loss of data?
This really depends on your priorities, i would have replaced my drives
well in advance of a similar situation.
The only reason i can imagine for splitting a disk into many partitions
and raiding them together is avoiding lenghty rebuilds when a single
drive is kicked from an array due to a correctable read error.
In practice the above scenario should not happen anymore, since md will
retry writing a stripe if it gets a read-error, besides you are planning
on using raid6, so a single drive failure will still leave you with a
nice degree of protection.

Regards,
L.

-- 
Luca Berra -- bluca@comedia.it
         Communication Media & Services S.r.l.
  /"\
  \ /     ASCII RIBBON CAMPAIGN
   X        AGAINST HTML MAIL
  / \

  parent reply	other threads:[~2009-07-03  6:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 15:22 RAID6 questions Marek
2009-07-02 16:23 ` Robin Hill
2009-07-02 16:27 ` Andre Noll
2009-07-02 16:42 ` Goswin von Brederlow
2009-07-02 16:53   ` Doug Ledford
2009-07-02 22:13   ` Greg Freemyer
2009-07-02 22:57     ` Goswin von Brederlow
2009-07-03  6:40 ` Luca Berra [this message]
2009-07-03  8:24   ` Goswin von Brederlow

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=20090703064003.GC23464@maude.comedia.it \
    --to=bluca@comedia.it \
    --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).