linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <ricwheeler@gmail.com>
To: David@santools.com
Cc: Keith Roberts <keith@karsites.net>, linux-raid@vger.kernel.org
Subject: Re: Two Drive Failure on RAID-5
Date: Thu, 22 May 2008 10:42:35 -0400	[thread overview]
Message-ID: <4835865B.4000501@gmail.com> (raw)
In-Reply-To: <122201c8bad9$0050f26a$3501a8c0@exchange.rackspace.com>

David Lethe wrote:
> the disk manufacturers stopped making them last year, and stopped R&D on them way before that.  
>
> -----Original Message-----
>
> From:  "Keith Roberts" <keith@karsites.net>
> Subj:  RE:  Re:  Re: Two Drive Failure on RAID-5
> Date:  Tue May 20, 2008 5:20 pm
> Size:  1K
> To:  "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
>
> On Tue, 20 May 2008, David Lethe wrote: 
>  
>   
>> To: Cry <cry_regarder@yahoo.com>, linux-raid@vger.kernel.org 
>> From: David Lethe <david@santools.com> 
>> Subject: RE:  Re:  Re: Two Drive Failure on RAID-5 
>>  
>> Here is a good analogy that puts this in perspective.  I haven't seen 
>> anybody equate the two yet, so get the name right if you quote this ;) 
>>
>> Disk drives are like light bulbs. You can buy the server class (similar 
>> to CFLs), or desktop (incandescent).  If you don't mind the dark, 
>> replace them as they fail, and buy spares as they go on sale. 
>> Conversely, if you have to maintain a vaulted ceiling chandelier, and 
>> are afraid of heights, then spending twice as much for never having to 
>> deal with *THAT* again will seem like a bargain. 
>>
>> - David Lethe 
>>     
>  
> So are there such things as server class EIDE drives? Or are  
> they all SCSI or SATA? 
>  
> Keith 
>   
Different vendors have different strategies around how to market their 
various drives - you have archival (think big, slow S-ATA for things 
like a Tivo), S-ATA drives that are consumer grade or slightly higher 
class drive like SAS (serial attached SCSI) and then the highest quality 
drives (Fibre channel).

You can get good results from all classes of drives, but you need to 
make sure that you periodically check them pro-actively for errors and 
try to repair them in place if possible. Also, make sure you get an 
updated kernel so we don't kick out drives that would be otherwise 
perfectly reasonable ;-)

ric


  reply	other threads:[~2008-05-22 14:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  0:24 Re: Re: Two Drive Failure on RAID-5 David Lethe
2008-05-22 14:42 ` Ric Wheeler [this message]
2008-05-22 16:16   ` David Lethe
  -- strict thread matches above, loose matches on Subject: below --
2008-05-19 22:49 Cry
2008-05-20  7:37 ` David Greaves
2008-05-20 15:32   ` Cry
2008-05-20 19:28     ` Brad Campbell
2008-05-20  9:14 ` David Greaves
2008-05-20 12:17   ` Janos Haar
2008-05-21 14:14   ` Cry
2008-05-21 20:15     ` David Greaves
2008-05-21 20:47       ` Janos Haar
2008-05-21 21:21         ` Cry
2008-05-22  8:38           ` David Greaves
2008-05-31  9:27             ` Cry
2008-05-22  0:05         ` Cry

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=4835865B.4000501@gmail.com \
    --to=ricwheeler@gmail.com \
    --cc=David@santools.com \
    --cc=keith@karsites.net \
    --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).