Page 2 of 4

Re: 2.1.6RC Feedback

PostPosted: Sun Oct 23, 2022 11:03 pm
by Jimbo
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:
  • 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?

Re: 2.1.6RC Feedback

PostPosted: Sun Oct 23, 2022 11:31 pm
by Jimbo
Ok, so more testing.

Creating a new pool in O3X 2.1.6 with:
Code: Select all
% sudo zpool create -f -o ashift=12 -o feature@head_errlog=disabled -o feature@zilsaxattr=disabled -O encryption=on -O keylocation=file:///Users/user/.keyFile -O keyformat=passphrase -O compression=lz4 -O atime=off -O casesensitivity=sensitive -O normalization=formD Data disk2


Builds a pool that can be imported and used into ZFS on Linux (zfs-2.1.6-1.fc36.x86_64) and into O3X 2.1.99test... however, after being used on 2.1.99, the pool cannot then be imported back into O3X. Weird. Same errors as reported above.

Update: Scratch that last bit. I can't get it to repoduce. A pool created with command above, imports into Linux, keys load but cannot mount, same input/output error and then pool has errors as reported earlier.

Re: 2.1.6RC Feedback

PostPosted: Sun Oct 23, 2022 11:46 pm
by lundman
Hmm, so maybe their fix is not to use three quotas, then the 2.1.99 "correction" we made will not be happy going forward.This might need new special case code for 2.1.99 version

Re: 2.1.6RC Feedback

PostPosted: Mon Oct 24, 2022 12:01 am
by Jimbo
There is definitely something squiffy going on here (it could be me)...

Pool built with
Code: Select all
sudo zpool create -f -o ashift=12 -o feature@head_errlog=disabled -o feature@zilsaxattr=disabled -O encryption=on -O keylocation=file:///Users/user/.keyFile -O keyformat=passphrase -O compression=lz4 -O atime=off -O casesensitivity=sensitive -O normalization=formD Data disk2
on O3X 2.1.6 has (in sequence):
  • Imported/keys loaded/mounted successfully into O3X 2.1.99.
  • Exported from O3X 2.1.99
  • Imported/keys loaded/mounted successfully into Linux 2.1.6.
  • Exported from Linux 2.1.6
  • Imported/keys loaded/DOES NOT mount into O3X 2.1.6RC - errors as reported earlier.

Will try this sequence again...

Re: 2.1.6RC Feedback

PostPosted: Mon Oct 24, 2022 12:24 am
by Jimbo
Jimbo wrote:There is definitely something squiffy going on here (it could be me)...

Pool built with
Code: Select all
sudo zpool create -f -o ashift=12 -o feature@head_errlog=disabled -o feature@zilsaxattr=disabled -O encryption=on -O keylocation=file:///Users/user/.keyFile -O keyformat=passphrase -O compression=lz4 -O atime=off -O casesensitivity=sensitive -O normalization=formD Data disk2
on O3X 2.1.6 has (in sequence):
  • Imported/keys loaded/mounted successfully into O3X 2.1.99.
  • Exported from O3X 2.1.99
  • Imported/keys loaded/mounted successfully into Linux 2.1.6.
  • Exported from Linux 2.1.6
  • Imported/keys loaded/DOES NOT mount into O3X 2.1.6RC - errors as reported earlier.

Will try this sequence again...


Yeah, if I create a new pool on O3X with this command, I can get it to import/load/mount with 2.1.99, export, and then load into Linxu 2.16, export, but then can only import/load but not mount back into O3X 2.1.6RC (errors as reported above). Attempting to create the pool in O3X 2.1.6, export and then import/load/mount into Linux 2.1.6 does not seem to work.

Re: 2.1.6RC Feedback

PostPosted: Mon Oct 24, 2022 4:15 pm
by lundman
OK if I add the compatibility back in, whats the best binary for you to test with, Monterey x86?

Re: 2.1.6RC Feedback

PostPosted: Mon Oct 24, 2022 7:02 pm
by Jimbo
lundman wrote:OK if I add the compatibility back in, whats the best binary for you to test with, Monterey x86?


I have a Monterey x86 12.6 VM I was testing with along with a physical, but the physical x86 machine I was testing on yesterday is now running Ventura. Montery will be fine for testing in the VM as I don't intend to upgrade that yet.

Re: 2.1.6RC Feedback

PostPosted: Mon Oct 24, 2022 8:57 pm
by lundman
Can you check this rc2 build? Catalina x86 should install on all newer OSes

OpenZFSonOsX-2.1.6rc2-Catalina-10.15.pkg
(16.24 MiB) Downloaded 212 times

Re: 2.1.6RC Feedback

PostPosted: Mon Oct 24, 2022 9:31 pm
by Jimbo
lundman wrote:Can you check this rc2 build? Catalina x86 should install on all newer OSes

OpenZFSonOsX-2.1.6rc2-Catalina-10.15.pkg


On it... I will report back soon.

Re: 2.1.6RC Feedback

PostPosted: Mon Oct 24, 2022 9:32 pm
by lundman
It contains some minor differences that we have with upstream, so lets try that first.

If still no good, we can put back the compat code we used to have