From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: David Lethe <david@santools.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Billy Crook <billycrook@gmail.com>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
Bill Davidsen <davidsen@tmr.com>, Neil Brown <neilb@suse.de>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Distributed spares
Date: Tue, 14 Oct 2008 16:37:56 +0200 [thread overview]
Message-ID: <20081014143755.GB3689@rap.rap.dk> (raw)
In-Reply-To: <2cda01c92e01$12827a4c$3e01a8c0@exchange.rackspace.com>
On Tue, Oct 14, 2008 at 08:30:00AM -0500, David Lethe wrote:
>
>
> Good to know. Could yo tell me if this is actually true for normal
> state-of-the art SATA disks, or only true for more expensive disks?
> Do you have a good reference for it.
>
>
> read the manual for any disk drive... They go into error detection, correction recovery algorithms and capability in great detail.
I don't get any manual when I buy a disk. Maybe you do - as you are
doing raid systems for your work.
I will see if I can dig upsome manuals on the net for the disks I have,
just to have some sense of what is state-of-the art.
best regards
keld
next prev parent reply other threads:[~2008-10-14 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 13:30 Distributed spares David Lethe
2008-10-14 14:37 ` Keld Jørn Simonsen [this message]
2008-10-14 15:18 ` David Lethe
2008-10-14 16:29 ` KELEMEN Peter
2008-10-14 17:16 ` David Lethe
2008-10-14 17:20 ` Mattias Wadenstein
-- strict thread matches above, loose matches on Subject: below --
2008-10-13 21:50 Bill Davidsen
2008-10-13 22:11 ` Justin Piszcz
2008-10-13 22:30 ` Billy Crook
2008-10-13 23:29 ` Keld Jørn Simonsen
2008-10-14 10:12 ` Martin K. Petersen
2008-10-14 13:06 ` Keld Jørn Simonsen
2008-10-14 13:20 ` David Lethe
2008-10-14 23:20 ` Bill Davidsen
2008-10-14 10:04 ` Neil Brown
2008-10-16 23:50 ` Bill Davidsen
2008-10-17 4:09 ` David Lethe
2008-10-17 13:46 ` Bill Davidsen
2008-10-20 1:11 ` Neil Brown
2008-10-17 13:09 ` Gabor Gombas
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=20081014143755.GB3689@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=billycrook@gmail.com \
--cc=david@santools.com \
--cc=davidsen@tmr.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=neilb@suse.de \
/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).