i've recently been re-introduced to OpenZFS and am excited to see the progress. really brilliant work, guys.
i work at a University (Schulich School of Music at McGill University). up to now, our ZFS archives are limited to our Solaris 11 machine. moving forward, we see a great need for a working, supportable cross-platform ZFS filesystem resource.
thus i have been testing 1.27 on a Mac (a Hackintosh for convenience switching between OS's) running 10.9.3, Solaris 11.1, and also on a (new) Mac Pro running 10.9.3. on the new Mac Pro, i have today installed 10.9.4 and the new OpenZFS 1.30 alpha released today.
here're my observations.
1.27 seemed to work well at first running on the Hackintosh, with two 3GB drives formatted with <zpool create -f -o version=28 -O version=5 -O compression=off Zpoolm1 raidz1 /dev/disk5 /dev/disk6>. the filesystem would always mount on Solaris 11.1 and was reliable under testing. on 10.9.3, booting from one other of my two boot drives would result in operations to a known-good zpool failing with a block (<zpool import Zpoolm1> is an uninterruptable blinking cursor). running Spindump from Activity Monitor yields this:
Process: zfs.util [412]
Path: /System/Library/Filesystems/zfs.fs/Contents/Resources/./zfs.util
Architecture: x86_64
Parent: diskarbitrationd [16]
Responsible: diskarbitrationd [16]
UID: 0
Task size: 505 pages
Importance: Adaptive, Donating
Thread 0xf34 DispatchQueue 1 priority 31
1001 start + 1 (libdyld.dylib) [0x7fff9610b5fd]
1001 main + 757 (zfs.util) [0x10e852935]
1001 zpool_import_by_guid + 329 (zfs.util) [0x10e853089]
1001 zpool_search_import + 255 (zfs.util) [0x10e864cef]
1001 zpool_find_import_impl + 1515 (zfs.util) [0x10e863e1b]
1001 pread + 10 (libsystem_kernel.dylib) [0x7fff91d67962]
*1001 hndl_unix_scall64 + 22 (mach_kernel) [0xffffff80002f3f46]
*1001 unix_syscall64 + 499 (mach_kernel) [0xffffff8000640a33]
*1001 pread_nocancel + 137 (mach_kernel) [0xffffff80005f2239]
*1001 ??? (mach_kernel + 4137150) [0xffffff80005f20be]
*1001 ??? (mach_kernel + 2046917) [0xffffff80003f3bc5]
*1001 VNOP_READ + 225 (mach_kernel) [0xffffff80003fe011]
*1001 spec_read + 414 (mach_kernel) [0xffffff800040d47e]
*1001 buf_biowait + 122 (mach_kernel) [0xffffff80003c796a]
*1001 msleep + 114 (mach_kernel) [0xffffff80005e3e42]
*1001 ??? (mach_kernel + 4078613) [0xffffff80005e3c15]
*1001 lck_mtx_sleep + 78 (mach_kernel) [0xffffff800022d18e]
*1001 thread_block_reason + 204 (mach_kernel) [0xffffff8000235d5c]
*1001 ??? (mach_kernel + 223579) [0xffffff800023695b]
*1001 machine_switch_context + 354 (mach_kernel) [0xffffff80002d8262]
the drives are not physically off-line, and are viewable in Disk Utility among other apps and utils.
also, when running 1.27 under 10.9.3 OR 1.30 under 10.9.4 on the new Mac Pro ALWAYS blocks. even if i "create" the zpool and am then able to see it, change permissions, and do disk performance tests on it), if i export it and try to re-import it, it blocks at exactly the same point (getting NO P_READ from the pread_nocancel call).
i'd like to troubleshoot this (am an experienced programmer), but am not able to do much without source code.
any suggestions?
George