RE: [t13] READ VERIFY SECTOR(S) (EXT) and NV cache command set

[Joseph Chen]

Title: READ VERIFY SECTOR(S) (EXT) and NV cache command set

Mark,   When the data had been placed on two locations we face issue of the consistency. The data from the media maybe difference from the NV due to some potential conditions: 1. Disc data is broken from grown defects. 2. NV data is broken due to flash grown defects.   One of the purpose for the READ VERIFY command, as it was used in some “format” verification, is to find defects and map out those potential area from system file table (FAT or MFT). When the host sends READ VERIFY command, the device does a read from the media, and validates the ECC result to decide if the data is good. However, many of the devices implement bad sector reassignment so the OS defect mapping usage becoming unnecessary.   It will be better to define a consistent location to verify instead of either or.   Regards, Joseph   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Overby Sent: Tuesday, July 11, 2006 11:03 AM To: forum@t13.org Subject: [t13] READ VERIFY SECTOR(S) (EXT) and NV cache command set   If you issue as READ VERIFY SECTOR(S) (EXT) to an LBA that is pinned in the NV cache, should it verify the cache, the media, or both? 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.