Can anyone tell me why successive runs of "zdb" would show very
different values for the cksum column? I had thought these counters were
"since last clear" but that doesn''t appear to be the case?
If I run "zdb poolname", right at the end of the output, it lists pool
statistics:
capacity operations bandwidth ----
errors ----
description used avail read write read write read
write cksum
data 1.46T 7.63T 117 0 7.89M 0 0
0 9
/dev/dsk/c0t210000D0230F0298d0s0 150G 781G 11 0 803K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d1s0 150G 781G 11 0 791K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d2s0 150G 781G 11 0 803K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d3s0 150G 781G 11 0 807K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d6s0 150G 781G 11 0 811K 0
0 0 2
/dev/dsk/c0t210000D0230F0298d7s0 150G 781G 12 0 817K 0
0 0 4
/dev/dsk/c0t210000D0230F0298d8s0 150G 781G 11 0 815K 0
0 0 4
/dev/dsk/c0t210000D0230F0298d9s0 150G 781G 11 0 797K 0
0 0 14
/dev/dsk/c0t210000D0230F0298d10s0 150G 781G 11 0 822K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d11s0 150G 781G 11 0 814K 0
0 0 4
If I run it again:
capacity operations bandwidth ----
errors ----
description used avail read write read write read
write cksum
data 1.46T 7.63T 108 0 5.72M 0 0
0 3
/dev/dsk/c0t210000D0230F0298d0s0 150G 781G 10 0 583K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d1s0 150G 781G 10 0 570K 0
0 0 19
/dev/dsk/c0t210000D0230F0298d2s0 150G 781G 11 0 596K 0
0 0 17
/dev/dsk/c0t210000D0230F0298d3s0 150G 781G 11 0 597K 0
0 0 3
/dev/dsk/c0t210000D0230F0298d6s0 150G 781G 10 0 591K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d7s0 150G 781G 11 0 586K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d8s0 150G 781G 10 0 591K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d9s0 150G 781G 10 0 569K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d10s0 150G 781G 10 0 586K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d11s0 150G 781G 10 0 589K 0
0 0 2
If I run "zdb -vs data" I get:
capacity operations bandwidth ----
errors ----
description used avail read write read write read
write cksum
data 1.46T 7.63T 70 0 4.27M 0 0
0 0
/dev/dsk/c0t210000D0230F0298d0s0 150G 781G 8 0 526K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d1s0 150G 781G 6 0 385K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d2s0 150G 781G 6 0 385K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d3s0 150G 781G 6 0 413K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d6s0 150G 781G 8 0 522K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d7s0 150G 781G 8 0 550K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d8s0 150G 781G 6 0 385K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d9s0 150G 781G 6 0 377K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d10s0 150G 781G 6 0 404K 0
0 0 0
/dev/dsk/c0t210000D0230F0298d11s0 150G 781G 6 0 422K 0
0 0 0
A zpool status shows:
pool: data
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool
can
still be used, but some features are unavailable.
action: Upgrade the pool using ''zpool upgrade''. Once this is
done, the
pool will no longer be accessible on older software versions.
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
c0t210000D0230F0298d0 ONLINE 0 0 0
c0t210000D0230F0298d1 ONLINE 0 0 0
c0t210000D0230F0298d2 ONLINE 0 0 0
c0t210000D0230F0298d3 ONLINE 0 0 0
c0t210000D0230F0298d6 ONLINE 0 0 0
c0t210000D0230F0298d7 ONLINE 0 0 0
c0t210000D0230F0298d8 ONLINE 0 0 0
c0t210000D0230F0298d9 ONLINE 0 0 0
c0t210000D0230F0298d10 ONLINE 0 0 0
c0t210000D0230F0298d11 ONLINE 0 0 0
Thanks,
Tristan
On 05.08.09 11:40, Tristan Ball wrote:> Can anyone tell me why successive runs of "zdb" would show very > different values for the cksum column? I had thought these counters were > "since last clear" but that doesn''t appear to be the case?zdb is not intended to be run on live pools. For a live pool you can use it with predictable results only on a dataset that does not change on disk, in other words snapshot, to dump objects in that dataset only. running it on a live pool may produce unpredictable results depending on a pool activity. victor> If I run "zdb poolname", right at the end of the output, it lists pool > statistics: > > capacity operations bandwidth ---- > errors ---- > description used avail read write read write read > write cksum > data 1.46T 7.63T 117 0 7.89M 0 0 > 0 9 > /dev/dsk/c0t210000D0230F0298d0s0 150G 781G 11 0 803K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d1s0 150G 781G 11 0 791K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d2s0 150G 781G 11 0 803K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d3s0 150G 781G 11 0 807K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d6s0 150G 781G 11 0 811K 0 > 0 0 2 > /dev/dsk/c0t210000D0230F0298d7s0 150G 781G 12 0 817K 0 > 0 0 4 > /dev/dsk/c0t210000D0230F0298d8s0 150G 781G 11 0 815K 0 > 0 0 4 > /dev/dsk/c0t210000D0230F0298d9s0 150G 781G 11 0 797K 0 > 0 0 14 > /dev/dsk/c0t210000D0230F0298d10s0 150G 781G 11 0 822K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d11s0 150G 781G 11 0 814K 0 > 0 0 4 > > If I run it again: > > capacity operations bandwidth ---- > errors ---- > description used avail read write read write read > write cksum > data 1.46T 7.63T 108 0 5.72M 0 0 > 0 3 > /dev/dsk/c0t210000D0230F0298d0s0 150G 781G 10 0 583K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d1s0 150G 781G 10 0 570K 0 > 0 0 19 > /dev/dsk/c0t210000D0230F0298d2s0 150G 781G 11 0 596K 0 > 0 0 17 > /dev/dsk/c0t210000D0230F0298d3s0 150G 781G 11 0 597K 0 > 0 0 3 > /dev/dsk/c0t210000D0230F0298d6s0 150G 781G 10 0 591K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d7s0 150G 781G 11 0 586K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d8s0 150G 781G 10 0 591K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d9s0 150G 781G 10 0 569K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d10s0 150G 781G 10 0 586K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d11s0 150G 781G 10 0 589K 0 > 0 0 2 > > If I run "zdb -vs data" I get: > > capacity operations bandwidth ---- > errors ---- > description used avail read write read write read > write cksum > data 1.46T 7.63T 70 0 4.27M 0 0 > 0 0 > /dev/dsk/c0t210000D0230F0298d0s0 150G 781G 8 0 526K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d1s0 150G 781G 6 0 385K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d2s0 150G 781G 6 0 385K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d3s0 150G 781G 6 0 413K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d6s0 150G 781G 8 0 522K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d7s0 150G 781G 8 0 550K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d8s0 150G 781G 6 0 385K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d9s0 150G 781G 6 0 377K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d10s0 150G 781G 6 0 404K 0 > 0 0 0 > /dev/dsk/c0t210000D0230F0298d11s0 150G 781G 6 0 422K 0 > 0 0 0 > > A zpool status shows: > > pool: data > state: ONLINE > status: The pool is formatted using an older on-disk format. The pool > can > still be used, but some features are unavailable. > action: Upgrade the pool using ''zpool upgrade''. Once this is done, the > pool will no longer be accessible on older software versions. > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > data ONLINE 0 0 0 > c0t210000D0230F0298d0 ONLINE 0 0 0 > c0t210000D0230F0298d1 ONLINE 0 0 0 > c0t210000D0230F0298d2 ONLINE 0 0 0 > c0t210000D0230F0298d3 ONLINE 0 0 0 > c0t210000D0230F0298d6 ONLINE 0 0 0 > c0t210000D0230F0298d7 ONLINE 0 0 0 > c0t210000D0230F0298d8 ONLINE 0 0 0 > c0t210000D0230F0298d9 ONLINE 0 0 0 > c0t210000D0230F0298d10 ONLINE 0 0 0 > c0t210000D0230F0298d11 ONLINE 0 0 0