I can only second @hedrick on his comment and as already written above, recommend everyone to build 2.2.2 by yourself. I am running 2.2.2 stable for a couple of weeks on mantic. I still have to fix one notebook here which got f**ked up (most likely) by this and reports no errors on a pool scrub but crashes with a ZFS kernel core dump on a `zdb -vvv -ccc POOL_NAME`. The pool is marked having errors and when you restart the machine works as if nothing ever happened. So it is a hidden ticking time bomb as you don't know when the system will crash. Unfortunately I wasn't able to narrow down the problem to a specific file system on the pool yet.
But I can only recommend to go with the full 2.2.2 patch set which has been tested by the ZFS dev team and a couple of highly motivated folks involved in fixing the bug(s) back then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
