linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Hill <robin@robinhill.me.uk>
To: "Peter W. Morreale" <morreale@sgi.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: implications of partitioning and raid
Date: Thu, 5 Jan 2012 16:12:17 +0000	[thread overview]
Message-ID: <20120105161217.GA23196@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <1325778034.4777.44.camel@hermosa.lnx.copansys.com>

[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]

On Thu Jan 05, 2012 at 08:40:34AM -0700, Peter W. Morreale wrote:

> 
> I'm wondering what the implications are for having multiple raid sets on
> a partitioned disk wrt to disk failures. 
> 
> For example, suppose I create two partitions on a set of disks and
> create raid sets on those partitions.  Further, not all raid sets
> reference the same disks.  IOW, md0 references disks 1 and 2, and md1
> references disk 1 and 3.  (overly simplistic for discussion purposes)
> 
> Assume a portion of disk 1 goes 'bad' (localized within one of those
> partitions), is noticed by md and a rebuild is warranted.  
> 
> What is the behavior?  
> 
Any failure will only affect the single array member where the error
occurred. In most cases this is due to a catastrophic disk failure
though, so will also occur on other partitions of the disk (and the
arrays using them) as well.

> Will both raid sets start a rebuild?  Or only the affected raid set?
> 
> IOW, would there be two rebuild tasks, one for each raid set?  Or a
> single rebuild that encompasses all raid sets (within the same raid
> level, of course) on the disk in question? 
> 
Rebuild processes are per raid set, but only one rebuild will be done at
a time using the same disk (so if disk 1 fails and is replaced, then
there's separate rebuilds pending for md0 and md1, but only one will run
at a time).

> What I am getting at is whether there would be any advantage to
> partitioning disks for failure purposes.   
> 
There's an advantage in being able to prioritise the rebuilds (so I can
rebuild the array containing / before that containing /opt for example)
and there's some cases where there's a transient failure (a write error
causes the array member to be failed, but testing shows up no errors) in
which case it reduces the rebuild time as only a single array needs to
be rebuilt. The latter is pretty rare though, unless you have other
underlying problems (such as power issues or poor quality I/O
chipsets/drivers).

HTH,
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-01-05 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 15:40 implications of partitioning and raid Peter W. Morreale
2012-01-05 16:12 ` Robin Hill [this message]
2012-01-06 11:34 ` Stan Hoeppner

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=20120105161217.GA23196@cthulhu.home.robinhill.me.uk \
    --to=robin@robinhill.me.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=morreale@sgi.com \
    /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).