FC4 kernel performance

[Charles Lopes]

Alan Cox wrote:

>On Wed, Jun 22, 2005 at 08:46:14AM -0500, Chris Adams wrote:
>  
>
>>Most things consider a bad sector a sign of a bad drive.  On today's
>>drives, where bad sectors are remapped internally to the drive, by the
>>time you see a bad sector, the drive has remapped a bunch of sectors
>>(and may be out of spare space).
>>    
>>
>
>Bad sector on write yes - that generally means its time to throw the drive
>away, on read its not neccessarily so bad. Thats one reaosn e2fsck will
>rewrite inode and other critical blocks that won't read as part of the
>recovery
>  
>
Isn't what RAID1 does already. My understanding was that in case of read 
error, it retries the read operation on a working mirror and rewrites 
the failed block. Can anyone confirm or infirm the RAID1 behaviour?