gcode-mirror / maczfs

Automatically exported from code.google.com/p/maczfs
Other
0 stars 0 forks source link

ZFS Ceases to Work After Update from 74.3.0 to 74.3.3 #137

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Reinstalling 74.3.0 fixes everything. Then installing 74.3.3 breaks everything 
again. Checksums are all correct for the 74.3.3 installer.

I'm on 10.7.5, on a Mac Pro 1,1. This is the relevant output I get for the 
non-working 74.3.3 using the diagnostic tool...notice a bunch of "malformed 
objects."

Would be grateful for you guys' advice...maybe there's an easy fix.

Determining system version
Looking for ZFS packages
Found 1 packages
Looking for installed ZFS modules and tools from packages ...
Found 4 ZFS related libraries, 1 ZFS kernel modules and 21 ZFS tools.
Looking for other zfs binaries
find: /usr/sbin/authserver: Permission denied
find: /opt/local: No such file or directory
Found 0 other ZFS related libraries, 0 other ZFS kernel modules, 6 other ZFS 
tools and  Launchd scripts.
Looking for version info in 1 found kext
Looking for version info in 27 found zfs tools
strings: for architecture i386 object: 
/usr/local/bin/zoink.dSYM/Contents/Resources/DWARF/zoink malformed object 
(offset field of section 0 in LC_SEGMENT command 3 not past the headers of the 
file)
strings: for architecture i386 object: 
/usr/sbin/zdb.dSYM/Contents/Resources/DWARF/zdb malformed object (offset field 
of section 0 in LC_SEGMENT command 3 not past the headers of the file)
strings: for architecture i386 object: 
/usr/sbin/zdb_static.dSYM/Contents/Resources/DWARF/zdb_static malformed object 
(offset field of section 0 in LC_SEGMENT command 3 not past the headers of the 
file)
strings: for architecture i386 object: 
/usr/sbin/zfs.dSYM/Contents/Resources/DWARF/zfs malformed object (offset field 
of section 0 in LC_SEGMENT command 3 not past the headers of the file)
strings: for architecture i386 object: 
/usr/sbin/zpool.dSYM/Contents/Resources/DWARF/zpool malformed object (offset 
field of section 0 in LC_SEGMENT command 3 not past the headers of the file)
strings: for architecture i386 object: 
/usr/sbin/ztest.dSYM/Contents/Resources/DWARF/ztest malformed object (offset 
field of section 0 in LC_SEGMENT command 3 not past the headers of the file)
strings: for architecture i386 object: 
/usr/sbin/ztest_static.dSYM/Contents/Resources/DWARF/ztest_static malformed 
object (offset field of section 0 in LC_SEGMENT command 3 not past the headers 
of the file)
Looking for version info in 4 found libraries
strings: for architecture i386 object: 
/usr/lib/libzfs.dylib.dSYM/Contents/Resources/DWARF/libzfs.dylib malformed 
object (offset field of section 0 in LC_SEGMENT command 2 not past the headers 
of the file)
strings: for architecture i386 object: 
/usr/lib/libzpool.dylib.dSYM/Contents/Resources/DWARF/libzpool.dylib malformed 
object (offset field of section 0 in LC_SEGMENT command 2 not past the headers 
of the file)
Looking for loaded kexts
Looking for panic reports
   /Library/Logs/DiagnosticReports/Kernel_2014-08-29-004849_michaeli.panic
   /Library/Logs/DiagnosticReports/Kernel_2014-08-30-045938_michaeli.panic
   /Library/Logs/DiagnosticReports/Kernel_2014-09-03-063523_michaeli.panic
   /Library/Logs/DiagnosticReports/Kernel_2014-09-13-233821_michaeli.panic
Found 4 MacZFS related panic logs out of 4 recorded panics.

Done.

You may examine the log file at 'collect-maczfs-state-info.txt' (current 
directory: /Users/michaeliadmin)
and then attach it to your problem report at 
'http://code.google.com/p/maczfs/issues/'.

Original issue reported on code.google.com by dmicha...@gmail.com on 14 Sep 2014 at 4:06

GoogleCodeExporter commented 9 years ago
Actually now it seems broken altogether! I tried to downgrade and now 
everything is *completely* messed up! Help!

zpool status
internal error: Unknown error: -1
Abort trap: 6

Original comment by dmicha...@gmail.com on 14 Sep 2014 at 4:13

GoogleCodeExporter commented 9 years ago
Quite simple.  This is most likely caused by an incomplete upgrade / downgrade.

To know for sure, I would have to look at the actual diagnostic output form the 
diagnostic tool, i.e. the file "collect-maczfs-state-info.txt", mentioned at 
the end of the progress output.

Simple fix:
Make sure the loaded kernel module "zfs.kext" matches the installed zfs tools 
and libraries.
You can check this with "kextstat". The zfs module should show version 74.3.3 
after you installed 74.3.3.

To get you system working, I'd suggest to check the module version with 
kextstat, and then run the installer that corresponds to the active module.
Then export all pools and unload the module.
Then install whatever version you want to use.
Then reboot.
(And in case your pools don't show up automatically, import them once manually.)

Original comment by googlelogin@bjoern-kahl.de on 14 Sep 2014 at 7:36

GoogleCodeExporter commented 9 years ago
Thanks! Uninstalling and then reinstalling the 74.3.0 version did the trick. I 
guess at some point soon I'll reattempt the upgrade after uninstalling 
everything again, including the zfs.kext. The only reason I'm trying the 
upgrade at all is that I've been getting kernel panics with CrashPlan's backup 
service. I'm hoping maybe things will be different with 74.3.3....

Original comment by dmicha...@gmail.com on 15 Sep 2014 at 12:49

GoogleCodeExporter commented 9 years ago
Glad to hear it works now.
The differences between 74.3.0. and 74.3.3 are not so big, so chances are the 
newer version doesn't help you.  You could open a new issue for the original 
problem (CrashPlan's crashes) and attach one or two panic reports.  Maybe one 
can say something more definite then.
In any case, if you are on a recent Mac OSX (Mavericks or newer) and don't need 
backward compatibility with older systems, you could also give O3X a try.  O3X 
is an alternative, newer implementation of ZFS running on recent Mac OSX 
versions.  You find the O3X community here: 
https://openzfsonosx.org/wiki/Main_Page

Original comment by googlelogin@bjoern-kahl.de on 15 Sep 2014 at 3:55