Page 1 of 2

Sequoia

PostPosted: Thu Jun 13, 2024 2:13 pm
by dmz
Obviously, it's not advisable to actually run a ZFS storage pool on an OS whose first developer seed came out 3 days ago. Still, I wanted to see if OpenZFS would even load, and it doesn't; what it does is this:

Code: Select all
Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection:
    1: One or more binaries has an error which prevented linking.  See other errors.
    2: Could not use 'org.openzfsonosx.zfs' because: Failed to bind '_sprintf' in 'org.openzfsonosx.zfs' (at offset 0x558 in __DATA_CONST, __auth_got) as could not find a kext which exports this symbol
org.openzfsonosx.zfs specific:
    1: Failed to bind '_sprintf' in 'org.openzfsonosx.zfs' (at offset 0x558 in __DATA_CONST, __auth_got) as could not find a kext which exports this symbol
" UserInfo={NSLocalizedDescription=Error occurred while building a collection:
    1: One or more binaries has an error which prevented linking.  See other errors.
    2: Could not use 'org.openzfsonosx.zfs' because: Failed to bind '_sprintf' in 'org.openzfsonosx.zfs' (at offset 0x558 in __DATA_CONST, __auth_got) as could not find a kext which exports this symbol
org.openzfsonosx.zfs specific:
    1: Failed to bind '_sprintf' in 'org.openzfsonosx.zfs' (at offset 0x558 in __DATA_CONST, __auth_got) as could not find a kext which exports this symbol
}

So, this is just a public service announcement to say, don't even try on Sequoia yet, because the kernel extension doesn't load. But it'd be interesting to see what happened if it could find something to replace the _sprintf function.

Re: Sequoia

PostPosted: Thu Jun 13, 2024 3:29 pm
by jeffc
Clang has already been complaining for some time whenever it sees sprintf being used. You probably need to switch to snprintf.

Re: Sequoia

PostPosted: Wed Jul 03, 2024 12:27 pm
by stefanwascoding
The changelog for the most recent release (https://openzfsonosx.org/wiki/Changelog#OpenZFS_on_OS_X_2.2.2_2023-12-05) mentions "don't use sprintf".

I'm assuming you did the test with the latest version, so probably not all uses of that function have been removed.

Re: Sequoia

PostPosted: Wed Aug 07, 2024 2:02 pm
by stefanwascoding
Turns out I was not looking at the right place, the News & Announcements part of the forum has actually offered a release candidate for a new version for quite a while: zfs-macOS-2.2.3rc5.

Tested quickly on Beta 5, and I could import & export my pool on an external SSD, as well as read/write data on it.

Re: Sequoia

PostPosted: Mon Sep 16, 2024 10:18 am
by dereed999
Is there an intel vs arm build for Sequoia for testing?

Re: Sequoia

PostPosted: Wed Sep 18, 2024 5:50 am
by jawbroken
just reporting that 2.2.3rc5 works for me on the release version of Sequoia (15.0). i did the OpenZFS update in Sonoma then upgraded to Sequoia.

Re: Sequoia

PostPosted: Fri Sep 27, 2024 7:51 am
by aplsms
Hello,
is it possible to have 2.2.3rc5 for intel platform?

Re: Sequoia

PostPosted: Fri Sep 27, 2024 9:17 am
by abc123
There's a Catalina build for x64 of 2.2.3rc5 which should work on all newer platforms.

Re: Sequoia

PostPosted: Fri Oct 11, 2024 9:09 am
by xenophon
Installed the current Catalina build (Intel) from June, with Sequoia fixes, but had to do the following:
- the installer (over the previous build) failed
- /var/log indicated that it could not unload the kext already present
- rebooted at this point and placed it on the desktop
- installed successfuly

Hope this helps.

Re: Sequoia

PostPosted: Mon Oct 21, 2024 6:05 am
by incumbent
jeffc wrote:Clang has already been complaining for some time whenever it sees sprintf being used. You probably need to switch to snprintf.


i have openbsd trauma that demands i use `vsnprintf` is that no longer a thing :lol:

trying an update now thanks for notes @xenophon