This message is from the T13 list server.
To answer question #2: A pinned LBA is pinned for all normal command accesses. So, if I boot a rescue CD that issues READ SECTOR and the LBA happens to be pinned, the drive will pull it out of the cache. I don't see the threat to data integrity in #3 On #1, yes - you have 3 potential "resting" locations for data (nv cache, volatile cache (traditional read / write cache), and the physical media) for a "hybrid" hard drive. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hale Landis Sent: Wednesday, July 12, 2006 3:11 PM To: [email protected] Subject: RE: [t13] READ VERIFY SECTOR(S) (EXT) and NV cache command set This message is from the T13 list server. Joseph Chen said: > When the data had been placed on two locations we face issue > of the consistency. 1) Aren't there really three locations? The NV cache, the normal drive cache/buffer and the media? 2) When is someone going to explain what happens if a drive that has an enabled NV cache with pinned data and it is accessed by a OS that doesn't know anything about NV cache? For example: If I boot one of those 'virus scan CDs' that really runs DOS or Ecos or Linux or some other OS... What happens if the virus scanner cleans a virus from sectors that are in the NV cache? Will those sectors also be updated on the media? 3) Will drives have a jumper that will enable/disable this extreme threat to data integrity? Hale -- Hale Landis -- [EMAIL PROTECTED] ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------
