On Sun, Jul 12, 2015 at 06:18:17PM -0700, Richard Elling wrote: > Some additional block pointer verification code was added in changeset > f63ab3d5a84a12b474655fc7e700db3efba6c4c9 and likely is the cause > of this assertion. In general, assertion failures are almost always software > problems -- the programmer didn't see what they expected.
If this is something that might have been ignored prior to this code change, maybe they could set aok to avoid panicking when they import the pool to recover data? Not very familiar with that technique myself but I've seen it mentioned frequently in cases like this, unless things have changed since then. _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss