I wrote that code several years ago. It is not quite the right way to go. zdb now does decompression, though slightly differently from what I implemented. Sy

I wrote that code several years ago. It is not quite the right way to go. zdb now does decompression, though slightly differently from what I implemented. Syntax is: zdb -R poolname vdev:offset:size:d The "d" at the end says to decompress. zdb tries different decompression algorithms until it finds one that is correct. As for my mdb changes, I really think mdb should be able to pick up kernel ctf info so that it can print data structures on disk. That I could probably get working on illumos fairly easily. My method used zdb to get the data uncompressed, then used mdb to print it out ala ::print. I actually think something like "offset::zprint [decompression] type" in mdb is the way to go. It would mean no need for zdb, which usually gives too much or not enough, and is not interactive (hence, not really a good debugger as far as I'm concerned). Better would be: # mdb -z poolname 20000::walk uberblock | ::print -t uberblock_t And from there, something like: offset::zprint lzjb objset_phys_t where offset comes from a DVA displayed in the uberblock_t. Some people seem to get my idea and think it's good. Others either don't get it, or don't care. Someone like Delphix might really like it. Just my 2 cents. max