I got another couple of days out of it without issue - so I think it's likely fixed.
It seems like this issue looks very similar to the following upstream bug, same behaviour but a different error, and so I wonder if it was ultimately the same bug. Looks like this patch from 2.0.3 was pulled into the package? https://github.com/openzfs/zfs/issues/11621 https://github.com/openzfs/zfs/issues/11474 https://github.com/openzfs/zfs/pull/11576 Further testing has been hampered as zsys deleted all of my home datasets entirely (including all snapshots) - tracked in https://github.com/ubuntu/zsys/issues/196 - using a non-zfs boot until I finish recovering that - but still seems likely fixed as I was hitting it most days before. ** Bug watch added: github.com/openzfs/zfs/issues #11621 https://github.com/openzfs/zfs/issues/11621 ** Bug watch added: github.com/openzfs/zfs/issues #11474 https://github.com/openzfs/zfs/issues/11474 ** Bug watch added: github.com/ubuntu/zsys/issues #196 https://github.com/ubuntu/zsys/issues/196 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
