I’m about to switch to OpenZFS for my upcoming 384GiB serious partition, which is to be shared between Artix, Void, FreeBSD, and Gentoos
Artix, Void, FreeBSD, and Gentoos all have native OpenZFS support
Gentoos include Funtoo, Mocaccino, and Calculate
Venom (an src-based distro like Gentoos) lneeds help from their founder to add OpenZFS native support by asking him

Good luck with it, it will all depend on the features enabled on the pools and the version of the software they run. They will need to be identical on every one of the OSs or it will fail. At least that is my experience with it and the supposed works on any. Oh then there will be the inevitable forced imports when you forget to export the pool before switching the OS.

And ... where are the exports of those pools supposed to be stored on? An USB storage?
Also, this also requires all those active runs in use on the zpools manually stopped before rebooting into the next OS also sharing those zpools right?
I mean in some ZFS manuals exporting zpools requires unmounting every active volumes under the pools

Not totally certain on the details. All I know is when I boot I see the zfs import pool from cache in the boot messages on my machines using it. They are imported automatically by the scripts or service installed when the zfs is. Now if you reboot into another OS using the zfs and try to access it tells you the pool is in use by another you must force the import if wanting to use it. That is where the errors can happen on the version/feature mis-match not allowing the use by older version and unsupported features on the version installed on that machine. Then if everything went fine you were able to use it and you are done with that OS then reboot into another the same forced import the pool is already in use happens once again, if you forgot to export it first. Universal works everywhere my behind. Export is not in the sense of storing something somewhere it is exporting the pool taking it offline for that machines OS that is currently using it. So yes everything mounted, running on it has to be stopped too. I was going to suggest the ext4 or similar file system for use on it, but the BSD is in there so perhaps a BSD file system that has Linux support would be the best to use. File systems are supposed to just work without this foolishness involved with the zfs implementation.

And forced imports from where? I guess nowhere other than the system in use on the zpools haven't been exported yet
Since the zpool is still in use on Artix (for example), but i rebooted unto Funtoo (another example), then back to Artix to export first, then to import on Funtoo?
How about on chroot sessions? When i imported the zpools on the host system could they be at once imported again on the chrooted guest?
If no i’m about to back to ext4 for that 384GiB partition which FreeBSD also has full supports on ext4

The last OS to have imported the pool is the one that has it in use even if not booted unless you export it before shutting down/rebooting. Yes the Artix and Funtoo example is what is needed to be done or on the Funtoo you just force the import. Chroot not a clue really my use of it is always with another OS going it to repair a broken one usually due to that piece of junk GRUB breaking the boot. I do not think you get the pool imported in there who knows only way to find out is try it. Really ext4 is your best bet all OSs support it and there is no advantage to using the zfs on a single drive other than the checksums of the files it does.

1 members found this post helpful.