Hello,
according to the comments, zap_cursor_serialize returns a cookie which
always has it's lower 4 bits set to 0.
However, while dtracing the cookie retunred by zap_cursor_serialize,
this does not appear to be the case. ie. I get values such as
--
bash-3.00# dtrace
Yeah...the ZFS team has since informed me of that... :-/ Thank you for the
reply though! It seems to me to be a highly undesired behavior when you're
running multiple zpools and multiple containers on top of them. As long as
you've got good pools running (and services on top of them), you probab
Is this on a 32-bit x86 kernel? zap_cursor_serialize() returns a
uin64_t, but DTrace is only capable of tracing the high-order portion of
this value (at least for the return probe). Looking at your output
below, it looks like you're only seeing 4 bytes of data, not 8.
- Eric
On Wed, Jun 21, 200
You failed two disks in the same raid-1 group?
If it so that unfortunately it is "expected" from ZFS to panic system.
--
This messages posted from opensolaris.org
