Jump to content

Data Integrity Field

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by W Nowicki (talk | contribs) at 21:46, 29 August 2013 (more context, seems to be in the SCSI standard?). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Data Integrity Field (DIF) was an approach to protect data integrity in computer data storage. It was proposed in 2003 by the T10 committee of the International Committee for Information Technology Standards.[1]

Packet-based storage transport protocols have CRC protection on command and data payloads. Interconnect buses have parity protection. Memory systems have parity detection/correction schemes. I/O protocol controllers at the transport/interconnect boundaries have internal data path protection. Data availability in storage systems is frequently measured simply in terms of the reliability of the hardware components and the effects of redundant hardware. But the reliability of the software, its ability to detect errors, and its ability to correctly report or apply corrective actions to a failure have a significant bearing on the overall storage system availability. The data exchange usually takes place between the host CPU and storage disk. There may be a storage data controller in between these two. The controller could be RAID controller or simple storage switches.

DIF included extending the disk sector from its traditional 512 bytes, to 520 bytes, by adding eight additional protection bytes.[1] This extended sector is defined for Small Computer System Interface (SCSI) devices, which is in turn used in many enterprise storage technologies, such as Fibre Channel.[2] An alternative technology called Protection Information was introduced in 2012.[3]

See also

References

  1. ^ a b Keith Holt (July 1, 2003). "End-to-End Data Protection Justification" (PDF). T10 Technical Committee document 03-224r0. Retrieved August 29, 2013.
  2. ^ "Data Integrity Extension" (PDF). T10 Technical Committee document 03-111r0. May 2, 2003. Retrieved August 29, 2013.
  3. ^ EMC Corporation (September 18, 2012). "An Integrated End-to-End Data Integrity Solution to Protect Against Silent Data Corruption" (PDF). White paper. Oracle Corporation. Retrieved August 29, 2013.