Re: 2.1.6RC Feedback
Posted: Sun Oct 23, 2022 11:03 pm
Well, if its just me hitting this, I'm happy to take the pain of migrating to new pools if the code then remains cleaner and closer to upstream.
However, this compatibilty issue would have to be clearly documented for anyone who is using ZFS native encryption prior to 2.1.6.
A couple of other points though after some more testing:
Is this still likely to be related to the MAC fixes you were referring to earlier given that the pool source is "current" Linux ZFS?
However, this compatibilty issue would have to be clearly documented for anyone who is using ZFS native encryption prior to 2.1.6.
A couple of other points though after some more testing:
- The encrypted test pool I created with 2.1.99 can be imported and mounted on Fedora with zfs-2.1.6-1.fc36.x86_64.
- A newly created encrypted test pool on Linux (zfs-2.1.6-1.fc36.x86_64) cannot be imported with O3X 2.1.6 - same errors I've described above (imports ok, key loads, will not mount (Input/output error) and then pool reports permanent errors.
Is this still likely to be related to the MAC fixes you were referring to earlier given that the pool source is "current" Linux ZFS?