[OmniOS-discuss] zdb -h bug?
Gary Gendel
gary at genashor.com
Tue Sep 15 23:18:22 UTC 2015
Paul,
I have a fresh install of OmniOS (installed 2 weeks ago and just updated).
zdb -h core dumps on both of these, both before and after the update.
Since I have nothing fancy (no cache or log disks), I suspect (and hope)
the problem is in zdb.
$ zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
archive 4.53T 1.49T 3.04T - 19% 32% 1.00x ONLINE -
rpool 278G 82.1G 196G - 10% 29% 1.00x ONLINE -
----------------------
$ zpool status
pool: archive
state: ONLINE
scan: scrub repaired 0 in 2h53m with 0 errors on Thu Sep 10 19:21:59 2015
config:
NAME STATE READ WRITE CKSUM
archive ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c3t0d0 ONLINE 0 0 0
c3t1d0 ONLINE 0 0 0
errors: No known data errors
pool: rpool
state: ONLINE
scan: scrub repaired 0 in 0h3m with 0 errors on Tue Sep 1 16:19:55 2015
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c2t0d0s0 ONLINE 0 0 0
c2t1d0s0 ONLINE 0 0 0
Gary
On 9/14/2015 9:50 PM, Paul B. Henson wrote:
> While trying to look for corruption from the recent L2 cache bug, I noticed
> that zdb core dumps trying to list the history on both my data pool (which
> had L2 cache) and my rpool (which did not). I'm wondering if there is some
> bug with zdb that is causing this as opposed to corruption of the pool.
>
> I'd be curious as to what 'zdb -h' does on the various pools out there,
> particularly ones created prior to 014 then subsequently upgraded to 014 but
> without large_blocks being enabled (as those are the characteristics of my
> pools :) ).
>
> If I get a little time I'm going to try to build a 012 box and simulate how
> my pools got to where they are and see if I can reproduce it.
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
More information about the OmniOS-discuss
mailing list