ercheck Report

Workspace:/export/jwadams/fma-cksum-events
Host:girltalk2
As of:Tue Aug 11 11:03:56 PDT 2009
Compare to:/net/dv11.sfbay/nfs2/dev/fma/gates/events-gate



Changes
payload version 0 for event:ereport.fs.zfs.checksum
Payload 0
Inherit version 0 from ereport
Inherit version 0 from ereport.fs
Inherit version 0 from ereport.fs.zfs
bad_cleared_bitsuint8_t[]Like bad_set_bits, but contains: (good data & ~(bad data)); that is, the bits set in the good data which are cleared in the bad data.
bad_cleared_histogramuint16_t[64]If this field exists, it is an array of counters. Each entry counts bit clears in a particular bit of a big-endian uint64_t. So the first entry counts clears of the the high-order bit of the first byte, the 9th byte, etc, and the last entry counts clears of the low-order bit of the 8th byte, the 16th byte, etc.
bad_range_clearsuint32_t[]This array has one element per range in bad_ranges. Each element contains the count of bits for that range which were set in the good data and clear in the bad data.
bad_range_setsuint32_t[]This array has one element per range in bad_ranges. Each element contains the count of bits in that range which were clear in the good data and set in the bad data.
bad_rangesuint32_t[][start, end) pairs of corruption offsets. Offsets are always be aligned on a uint64_t boundry, and can include some gaps of non-corruption. (See bad_ranges_min_gap)
bad_ranges_max_gapuint32_tIn order to bound the size of the bad_ranges array, gaps of non-corruption <= bad_ranges_max_gap bytes have been merged with adjacent corruption. Always at least 8, since we look at corruption on a uint64_t basis.
bad_set_bitsuint8_t[]If this field exists, it is an array of: (bad data & ~(good data)); that is, the bits set in the bad data which are cleared in the good data. Each element corresponds a byte whose offset is in a range in bad_ranges, and the array is in offset-order. (i.e. the first element is the first byt in the first bad_ranges range, and the last element is the last byte in the last bad_ranges range)
bad_set_histogramuint16_t[64]If this field exists, it is an array of counters. Each entry counts bit sets in a particular bit of a big-endian uint64_t. So the first entry counts sets of the the high-order bit of the first byte, the 9th byte, etc, and the last entry counts sets of the low-order bit of the 8th byte, the 16th byte, etc.
cksum_actualuint64_t[]The actual checksum value for the bad block
cksum_algorithmstringChecksum algorithm used
cksum_byteswapstringWhether or not the data was byteswapped
cksum_expecteduint64_t[]The expected checksum value for the block
parent_devidstringZFS vdev parent device id
parent_guiduint64_tZFS vdev parent guid
parent_pathstringZFS vdev parent path
parent_typestringZFS vdev parent type
vdev_devidstringZFS vdev device id
vdev_guiduint64_tZFS vdev guid
vdev_pathstringZFS vdev path
vdev_typestringZFS vdev type
zio_blkiduint64_tZFS block id
zio_errint32_tZFS IO errno
zio_levelint32_tZFS indirect level
zio_objectuint64_tZFS object
zio_objsetuint64_tZFS objset
zio_offsetuint64_tZFS vdev offset
zio_sizeuint64_tZFS vdev size







ARC review is required.



End of ercheck report, errors found: 0