OpenZFS-2.0-release report

[lundman]

I think maybe "zfs recv" of a zvol will deadlock at the end when it tries to create the disk for it. Investigating.

[lundman]

OK posted a new build, now the zfs-tests pass (without panic).

[Sharko]

I'll be excited to test it on Mojave, when you have a chance to prepare the package. Would I be correct to assume that this new release is like the previous versions with respect to delegation, .i.e. not supported yet? One of these I really should clone the repository and look into what it would take to get that working.

[lundman]

Yeah, not had time to look at delegation - I don't think it would be particularly hard, just needs to be tested so we don't accidentally give root when we shouldn't.

[theit]

Trying to install OpenZFSonOsX-2.0.0-Catalina-10.15.pkg results in an error message on my machine:

1) According to the system preferences panel it is blocked because the app isn't from a verified developer.
2) The Finder shows a message it can't be opened because Apple could not scan for malware in it.

Do you know what is causing this?

[lundman]

Hmm? Are we saying the pkg isn't notarized? That seems odd, other Cataliina users have installed it..

[rcfa]

So, I installed the latest release candidate package for Big Sur.

The console is full of these:

Code: Select all

Dec  9 23:13:21 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Dec  9 23:13:31 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed[3530]): Service exited with abnormal code: 1
Dec  9 23:13:31 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Dec  9 23:13:41 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed[3531]): Service exited with abnormal code: 1
Dec  9 23:13:41 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Dec  9 23:13:51 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed[3532]): Service exited with abnormal code: 1
Dec  9 23:13:51 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Dec  9 23:14:01 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed[3533]): Service exited with abnormal code: 1
Dec  9 23:14:01 mymac com.apple.xpc.launchd[1] (org.openzfsonosx.zed): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.


Manually loading the module works:

Code: Select all

# kmutil showloaded | grep zfs                                                                                   1 ⨯
No variant specified, falling back to release
  211    0 0xffffff7fa252c000 0x328000   0x328000   net.lundman.zfs (2.0.0) 72483E1E-DD77-3873-BC77-C1B8AFF10A58 <30 8 6 5 3 1>


However issuing any zfs related command gets me this:

Code: Select all

# zpool list
The ZFS modules are not loaded.
Try running '/sbin/kextload zfs.kext' as root to load them.


I assume this is, from searching around here, due to the lack of creation of the /dev/zfs device node.

How do I create a node?

Thanks!

[Jimbo]

You didn’t mention - have you enabled keepsyms=1?

Ref (and related earlier posts):
viewtopic.php?f=26&t=3469&start=50#p10656

Hopefully this will be fixed at some point.

Cheers!

[rcfa]

You didn’t mention - have you enabled keepsyms=1?

Ref (and related earlier posts):
viewtopic.php?f=26&t=3469&start=50#p10656

Hopefully this will be fixed at some point.

If that was directed at me, the short answer is "NO"

I didn't thing that was relevant, as the thread where I read about it was related to kernel panics, of which I have none.
I simply have the issue that it wont do anything, even if the extension is loaded into the kernel.

So I'll change that. Plus, I'm also updating to the macOS 11.1 release candidate. I'll see how things go after all that's said and done...

[rcfa]

OK, that seems to have fixed it.

Great!

Suggestion: if this isn't something that's fixable for the 2.0 release, it would be useful if during installation that would be pointed out, or if the installer script would simply append it to the nvram boot-args string automatically, and let the user know it (had to).

Otherwise people are going to wreck their heads about it.

Anyway, great to have ZFS back on Big Sur!