OpenZFS on OS X

Ah if only I had waited a bit longer eh.

OK, so looks like we should push out a 2.2.2 release somewhat urgently, but let's collect any issues here:

* Monterey-arm64 "patch" file check
* 10.9 still pops up "disk is unreadable" but dunno if energy into 10.9 is worth it
* .in files are left after install (everywhere? or just some places?)

What sort of timeline are you thinking for this new release? I could possibly load the current 2.2.0 release this week and do some playing around under Monterey x86 on the venerable Mac Pro 5,1.

No further show-stoppers in 2.2.0 ? I will start to roll out.

I have posted a pkg installer for intel and arm64. If it is convenient for you to test, please do so. I'll start building for the rest in a little while.

lundman wrote:
* 10.9 still pops up "disk is unreadable" but dunno if energy into 10.9 is worth it

20 persons downloaded v2.2.0-MAVERICKS-10.9.pkg... we surely understand you don't want to spend much time for us, but if you do, you'll make 20 persons happy.
The point is that we probably don't use exclusively 10.9, but having a working ZFS version across all our MacOS machines (different versions of the OS) would be great. I currently keep 1.9.2 on 10.9 and can't upgrade my pools if I want full compatibility.

nodarkthings wrote: but if you do, you'll make 20 persons happy

You could try chase it down on your own? It basically is an interaction between
/Library/Filesystems/zfs.fs/Info.plist - in particular the FSProbeOrder
the tool it executes: "zfs_util" and the return codes it replies with, it is called for each disk (or was it each partition) and it replies depending on it recognising it.

So one start point would be to rename "zfs_util" to "zfs_util.orig" and put in a bash script named "zfs_util", which can just return FSUR_RECOGNIZED (-1) - this will
show that the popups go away, but also break inserting a FAT32 drive etc. And play with it until you can figure out what goes wrong. Perhaps "zfs_util" is at a too high FSProbeOrder, perhaps it fails to say FSUR_RECOGNIZED when it should etc.

Then make a PR for the fix

Thanks for the new release... it seems not to install correctly on Sonoma 14.1.2 (the arm64-version on Macmini M2 Pro):

Code: Select all

zfs version
zfs-2.2.2-1
zfs-kmod-2.2.0-1


The kmod is still 2.2.0-1. Sometimes the kmod has only been upgraded after running the installer twice. This time, even after 5 times running the installer, nothing changes. The System Settings are opened, but there is no (new) kernel extension to accept... because it isn't new.

lundman wrote:

nodarkthings wrote: but if you do, you'll make 20 persons happy

You could try chase it down on your own?

Thanks for the suggestion, I would do it happily but I'm afraid it's a bit beyond my knowledge as I'm little more than a basic user. I'll try it when I understand what you wrote and let you know if I find anything.

Thanks for the suggestion, I would do it happily but I'm afraid it's a bit beyond my knowledge as I'm little more than a basic user. I'll try it when I understand what you wrote and let you know if I find anything.

I was the same though, knew nothing of this area. I'm just a tiny bit ahead in experience, that is all

I think I would replace zfsutil with shell script that returns RECOGNISED, which "in theory" should remove popups, then start whittling down.

Thank you!
I'll answer on that thread: viewtopic.php?f=24&t=3861 for not polluting this one.