linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Brendan Hide <brendan@swiftspirit.co.za>
Cc: linux-raid@vger.kernel.org
Subject: Re: making a hot spare ... hot
Date: Wed, 21 Sep 2011 14:05:51 +1000	[thread overview]
Message-ID: <20110921140551.31828ea9@notabene.brown> (raw)
In-Reply-To: <4E795A49.1060000@swiftspirit.co.za>

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

On Wed, 21 Sep 2011 05:30:17 +0200 Brendan Hide <brendan@swiftspirit.co.za>
wrote:

> Hi all
> 
> To the point: When a disk is designated as a hot spare, would it be of 
> benefit to spread copies of data chunks from the other disks onto the 
> hot spare even before a failure? Has this been tried before?
> 
> If its not already being done, it'd have a small positive consequence 
> for performance as well as data integrity, with relatively little to no 
> negative consequences. Benefits would diminish the larger the array, 
> much like the performance difference between raid3 and raid5. Read 
> speeds would theoretically increase and write speeds should not decrease 
> except in the case of poor hardware.
> 
> Given a 6-disk raid5 (5 "data" disks + 1 spare) array, a re-sync will 
> start at 25% progress from the moment a disk gets dropped out of the 
> array. The theoretical max read speed will also increase by 16% by 
> reading from 6 disks instead of 5. The cons will be that, when writing, 
> an extra write will need to occur to the "spare" disk. Though this 
> shouldn't have any performance penalties on modern hardware I can still 
> see it as being a concern.
> 
> I suspect something like this might have been suggested before - but I 
> haven't been able to find any reference to something along these lines 
> online. I'll welcome any discussion or links to relevant information.
> 
> Thanks.
> 
> Key:
> 0-F: Data Chunks
> P: Parity
> 
> Layout of standard RAID5 + 1 standard spare
> 
> Disk0: 048C
> Disk1: 159P
> Disk2: 26PD
> Disk3: 3PAE
> Disk4: P7BF
> Disk5: Spare (empty)
> 
> Chunks read per read "cycle": 5
> Time to read all 16 data chunks: 4 cycles
> 
> Layout of standard RAID5 + 1 "hot" spare:
> Disk0: 048C
> Disk1: 159P
> Disk2: 26PD
> Disk3: 3PAE
> Disk4: P7BF
> Disk5: 05AF
> 
> Chunks read per "cycle": 6
> Time to read all 16 data chunks: 3 cycles
> 

I see what you are getting at, but I doubt the value justifies the extra
complexity.
If you want more redundancy and have a spare device - use RAID6.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2011-09-21  4:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21  3:30 making a hot spare ... hot Brendan Hide
2011-09-21  4:05 ` NeilBrown [this message]
2011-09-21  6:59   ` Brendan Hide
2011-09-21  7:18     ` David Brown

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=20110921140551.31828ea9@notabene.brown \
    --to=neilb@suse.de \
    --cc=brendan@swiftspirit.co.za \
    --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).