Re: AW: data corruption - the nightmare continues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 20, 2002 at 04:57:33PM +0100, Martin Bene wrote:
> Hi Jakob,
> 
> > To me it has been fairly common.
> 
> I can confirm that, I've also seen this a few times.

Actually, a year or so back, I didn't see this. But the past half year or few
months at least I've had heaps of disks do this...  IBM...  Not just GXP75,
or whatever the name of the "doomed series" were.

...
> As long as we're talking about raid5 or raid1, you should still be able to get the correct data from the raid device, use this to try a rewrite after a read error. if the write works and a read afterwards works as well => don't kick the disk.
> 
> Having this functionality could be worthwile; of course if this triggers, it should write a warning to syslog.

Hmm.  I suppose you're right - that would be neat indeed.

Cheers,

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:
-
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux