linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Lethe" <david@santools.com>
To: "Keld Jørn Simonsen" <keld@dkuug.dk>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: 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 8:30:00 -0500	[thread overview]
Message-ID: <2cda01c92e01$12827a4c$3e01a8c0@exchange.rackspace.com> (raw)



-----Original Message-----

From:  Keld Jørn Simonsen <keld@dkuug.dk>
Subj:  Re: Distributed spares
Date:  Tue Oct 14, 2008 8:06 am
Size:  1K
To:  "Martin K. Petersen" <martin.petersen@oracle.com>
cc:  "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>

On Tue, Oct 14, 2008 at 06:12:29AM -0400, Martin K. Petersen wrote: 
> >>>>> "Keld" == Keld Jørn Simonsen <keld@dkuug.dk> writes: 
>  
> Keld> I have also been thinking a little on this. My idea is that if 
> Keld> bit errors develop on disks, then there is first maybe one bit 
> Keld> error, and the crc check on the disk sectors then finds and 
> Keld> corrects these. 
>  
> Keld> If you rewrite such bit errors, then that bit error will be 
> Keld> corrected, and you prevent the one-bit error from developing to 
> Keld> a two-bit error that is not correctable by the CRC. 
>  
> I think you are assuming that disks are much simpler than they 
> actually are. 
>  
> A modern disk drive protects a 512-byte sector with a pretty strong 
> ECC that's capable of correcting errors up to ~50 bytes.  Yes, that's 
> bytes. 
>  
> Also, many drive firmwares will internally keep track of problematic 
> media areas and rewrite or reallocate affected blocks.  That includes 
> stuff like rewriting sectors that are susceptible to bleed due to 
> being adjacent to write hot spots. 
 
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. 
 
best regards 
keld 
-- 
To unsubscribe from this list: send the line "unsubscribe linux-raid" in 
the body of a message to majordomo@vger.kernel.org 
More majordomo info at  http://vger.kernel.org/majordomo-info.html 
 
read the manual for any disk drive... They go into error detection,  correction recovery algorithms and capability in  great detail.  
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2008-10-14 13:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 13:30 David Lethe [this message]
2008-10-14 14:37 ` Distributed spares Keld Jørn Simonsen
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='2cda01c92e01$12827a4c$3e01a8c0@exchange.rackspace.com' \
    --to=david@santools.com \
    --cc=billycrook@gmail.com \
    --cc=davidsen@tmr.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=keld@dkuug.dk \
    --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).