Based on inspecting the ZFS source code, this looks like a ZFS inode where there is a mismatch between the claimed size of the inode's (ZFS) ACL and how it's stored. If you're willing to do some work, it might be possible to narrow this down to identify a specific inode and what's wrong with it, which could help fixing this (in Ubuntu and upstream). Unfortunately this will be a somewhat involved process involving zdb, because you need to dump on-disk structures. If you're interested and willing to tackle this, your best approach is probably to ask for help on the ZFS on Linux mailing list, because it will be easier to give the details there.
It is possible that a 'zfs send | zfs receive' sequence will allow you to recover a usable version of the filesystem (and I believe you can do this without the filesystem being mounted and thus without the risk of panic). If you have, say, a spare external USB drive, it might be worth trying this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788004 Title: File System inaccessible after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1788004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
