After updating to 10.9 can't get auto mount to work

[GoogleCodeExporter]

After updating to 10.9 can't get auto mount to work.

1. Installed MacZFS-74.3.1-Mavericks.pkg
2. Importing my old zpool worked fine and mount it ok. 
3. I installed the maczfs_launchd_scripts-0.1.0.tar.bz2 scripts.

On reboot I get an error, checking the logs I get:

Process:         zfs.util [38]
Path:            /System/Library/Filesystems/zfs.fs/zfs.util
Identifier:      zfs.util
Version:         ???
Code Type:       X86-64 (Native)
Parent Process:  diskarbitrationd [18]
Responsible:     diskarbitrationd [18]
User ID:         0

Date/Time:       2013-10-29 23:24:10.186 +0000
OS Version:      Mac OS X 10.9 (13A603)
Report Version:  11

Crashed Thread:  0

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /usr/lib/libzfs.dylib
  Referenced from: /System/Library/Filesystems/zfs.fs/Contents/Resources/../../zfs.util
  Reason: Incompatible library version: zfs.util requires version 1.0.0 or later, but libzfs.dylib provides version 0.0.0

Binary Images:
    0x7fff618a9000 -     0x7fff618dc817  dyld (239.3) <D1DFCF3F-0B0C-332A-BCC0-87A851B570FF> /usr/lib/dyld

If I login as my backup user and import the zpool then logout, when I try to 
login as my primary user (home dir on spool) my machine dies then gives me an 
grey error screen instructing me to restart.

Any help would be much appreciated.

Thanks.

Original issue reported on code.google.com by jmdrawn...@googlemail.com on 30 Oct 2013 at 12:02

[GoogleCodeExporter]

Admin please remove this.

Original comment by jmdrawn...@googlemail.com on 4 Nov 2013 at 10:03

[GoogleCodeExporter]

Dear  jmdrawneek,

You wrote "Admin please remove this.", so have you been able to resolve the 
problem?
If yes, I can close this report.  Else I'd like to understand the problem.

Original comment by googlelogin@bjoern-kahl.de on 22 Nov 2013 at 9:39

[GoogleCodeExporter]

Yes I have thanks. Got the latest launchdaemon.

Thanks!

Original comment by jmdrawn...@googlemail.com on 22 Nov 2013 at 9:41

[GoogleCodeExporter]

Dear all

I can confirm that this issue exists: I had zfs running for an
external firewire disk since about August (pre Mavericks) without
problems.  Upgraded to Mavericks, still no issues.  Then I tried to do
a "git clone ..." of a repository in the pool and got a kernel panic.
Reproducibly.  Assumed it was an issue with the OS upgrade.  
Upgraded to the latest maczfs for Mavericks and zfs won't start anymore.

So please do not remove this issue!

The message indicates a version mismatch between zfs.util and libzfs.
Checking with otool gives:

thomasbrupbacher(Mac-mini)209$ otool -L 
/System/Library/Filesystems/zfs.fs/zfs.util
/System/Library/Filesystems/zfs.fs/zfs.util:
    /usr/lib/libzfs.dylib (compatibility version 1.0.0, current version 1.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
thomasbrupbacher(Mac-mini)210$ otool -L /usr/lib/libzfs.dylib
/usr/lib/libzfs.dylib:
    /usr/lib/libzfs.dylib (compatibility version 0.0.0, current version 1.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)

I am not a Mac developper and have not looked into the version
numbering scheme (my background is FreeBSD), but this seems OK.

Checking the files themselves shows that not both files have the same date:

thomasbrupbacher(Mac-mini)241$ ll /System/Library/Filesystems/zfs.fs/
total 56
drwxr-xr-x   4 root  wheel    136 Apr  2  2013 ./
drwxr-xr-x  18 root  wheel    612 Oct 25 09:18 ../
drwxr-xr-x   5 root  wheel    170 Apr  2  2013 Contents/
-rwxrwxr-x   1 root  wheel  25968 Apr  2  2013 zfs.util*
thomasbrupbacher(Mac-mini)244$ ll /usr/lib/libzfs.dylib
-rwxrwxr-x  1 thomasbrupbacher  staff  638224 Oct 28 21:59 
/usr/lib/libzfs.dylib*

Checking the contents of the package (MacZFS-74.3.1-Mavericks.pkg)
shows that also zfs.util should have a date from October.  So I did a
manual install (see wiki) and now everything is fine again.

Bottom line: when upgrading to the new Mavericks package, it is
possible that not all files are upgraded and a manual upgrade is needed.

Cheers, Thomas

Original comment by thomas.b...@gmail.com on 26 Nov 2013 at 10:12

[GoogleCodeExporter]

I have uploaded a new installer.  Can you check MacZFS-74.3.2 ?

Also, can you run a "find /usr /System /opt /Library -iname '*zfs*' -a -type f 
-a -ls" after the new install?  It should only list files newer then Nov. 24. 

Original comment by googlelogin@bjoern-kahl.de on 27 Nov 2013 at 9:16

[GoogleCodeExporter]

I installed 74.3.2 and ran find.  All zfs relevant files have now a date of 27 
Nov.

After a restart everything seems fine (no logs about crashes, zfs volume is 
mounted and accessible).

Thanks for fixing this!

Original comment by thomas.b...@gmail.com on 28 Nov 2013 at 9:42

[GoogleCodeExporter]

Ok, thanks for reporting back. Closing this.

Original comment by googlelogin@bjoern-kahl.de on 29 Nov 2013 at 9:44

• Changed state: Done