This message is from the T13 list server.
Auto-relocation also MUST not take place until valid data is available. The non-recovered error should go into the "Pending" list (waiting for a write or a recovered read). Then, when the write occurs, the sector from the "Pending" list should be tested first before re-assignment. WriteLong should NEVER cause re-assignment. ...Harlan >This message is from the T13 list server. > > >Creat a false uncorrectable error is only done in the very beginning of >using the drive as RAID1 rebuild target drive (and only if necessary, i.e. >only when the source drive has reported an unrecoverable data block). It >might affect the statistical data the drive collected a little bit (only the >drive guys can answer this). Auto-relocation should not be affected because >this is not a normal write error. > >Raymond Liu > >-----Original Message----- >From: Hale Landis [mailto:[EMAIL PROTECTED]] >Sent: Thursday, March 21, 2002 10:02 AM >To: T13 List Server >Subject: [t13] RAID and R/W LONG > > >This message is from the T13 list server. > > >On Thu, 21 Mar 2002 09:18:13 -0800, [EMAIL PROTECTED] wrote: >>This message is from the T13 list server. >>[...] you might implement >>vendor specific commands to "address" that >>(which will keep the R/W Long >>still formally in "obsolete" state)? > >Raymond, I think I asked a few days ago, but could you explain in >detail why/how you are using R/W LONG? Do you expect the command to >actually be passed to a drive behind a RAID controller or is the >command executed directly and only by the RAID controller? If the >command is used to create a false uncorrectable error on a real >drive, how do you then adjust for the possible effects on the drive's >SMART data or the drives auto-relocation function? > > > >*** Hale Landis *** www.ata-atapi.com *** > >
