linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Dan Stromberg <strombrg@dcs.nac.uci.edu>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: number of global spares?
Date: Wed, 28 Sep 2005 15:11:16 -0400	[thread overview]
Message-ID: <433AEAD4.3070801@tmr.com> (raw)
In-Reply-To: <17167.40479.3220.155672@cse.unsw.edu.au>

Neil Brown wrote:

>On Friday August 26, strombrg@dcs.nac.uci.edu wrote:
>  
>
>>I've been working on a RAID setup with dual RAID controllers and
>>three expansion boxes - 48 disks in all, including data, parity and
>>global spares.
>>    
>>
>
>If there are 48 drives, why do your drive-numbers go up to 59?
>Confusing but not important.
>
>Presumably these are 360G drives (or there abouts) and you are hoping
>to use about 42 for data and the remaining 6 for redundancy.
>
>I feel this a bit tight but could be workable.
>
>If you were using Linux-soft-raid, I would probably suggest 3 16-drive raid6
>arrays, possibly making 1 a 15 drive raid6 so there is one global spare.
>However I gather you are using hardware RAID - do the controllers
>support RAID6 ??
>  
>
>>Please be sure to use a fixed-pitch font when viewing the tables found
>>below.  BTW, if people weren't so terrified of HTML, I could just make a
>>nice HTML table for easy reading without silly font requirements...
>>    
>>
>
>You mean some mail readers use variable-width-fonts to display
>text/plain?  How broken!
>  
>
Some clients actually do what the user asks in 'preferences' which may 
not be fixed fonts...

More to the point, is there a nice widely accepted calculation for 
reliability vs. MTBF? I started to develop one but stopped because it 
isn't really much use without the S.D. of the MTBF. If drive MTBF is 
equal, the better drive (safer) is one with more S.D. rather than a 
clustering of failures which somewhat increases the chance of a failure 
during rebuild.

The better the quality control the higher the risk of failure clusters, 
unfortunately.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  parent reply	other threads:[~2005-09-28 19:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 19:00 number of global spares? Dan Stromberg
2005-08-26 22:21 ` Mark Hahn
2005-08-27  6:02   ` Dan Stromberg
2005-08-27 19:28     ` Mark Hahn
2005-08-26 22:56 ` Neil Brown
2005-08-27  5:50   ` Dan Stromberg
2005-09-28 19:34     ` Bill Davidsen
2005-09-28 19:11   ` Bill Davidsen [this message]
2005-08-26 23:21 ` Guy
2005-08-27  5:00   ` Daniel Pittman
2005-08-27  5:33     ` Dan Stromberg
2005-09-28 19:47       ` Bill Davidsen
2005-09-28 19:58         ` Dan Stromberg
2005-08-27  5:42   ` Dan Stromberg

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=433AEAD4.3070801@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=strombrg@dcs.nac.uci.edu \
    /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).