Time to re-up this thread... > On Feb 29, 2016, at 10:25 AM, Dan McDonald <[email protected]> wrote: > > Someone pinged me unicast about OmniOS crashing with a stack trace during > mount - migrating from OI to OmniOS - and crashing in > zap_leaf_lookup_closest(). > > Looking up zap_leafe_lookup_closests in the illumos bug database, I've found > two freezes (1305 and 2233), two panics that look like they may have been > cured by Justin Gibbs's 5056 fix (3320 and 4432), and two that look IDENTICAL > to the unicast ping: > > https://illumos.org/issues/5833 > > https://illumos.org/issues/6510
I have a customer who has a box that panics on OmniOS r151014, but with a pool that was created by r151010, which does NOT contain the Justin Gibbs 5056 fix. This customer has it narrowed to ONE dataset. It's on a massive pool however. Is there zdb(1M) magic I can perform to just inspect the one dataset's stuff? He can panic the machine if he mounts this dataset, but if he doesn't, things are good. Thanks, Dan ------------------------------------------- openzfs-developer Archives: https://www.listbox.com/member/archive/274414/=now RSS Feed: https://www.listbox.com/member/archive/rss/274414/28015062-cce53afa Modify Your Subscription: https://www.listbox.com/member/?member_id=28015062&id_secret=28015062-f966d51c Powered by Listbox: http://www.listbox.com
