Hello, I've a problem that a harddrive formatted with ZFS via OSX kills my FBSD. Two kernel panics occur when attaching a ZFS volume created by OSX Snow Leopard (10.6.2). ZFS Volumes create with FreeBSD are running fine. I also played around with enabling/disabling ZIL, prefetch, adjusting memory usage... the result was always the same. It would be nice if you could help here. Best Regards, Stefan How-To-Repeat: Create a ZFS Disk with OSX Snow Leopard and plug it into the FreeBSD machine. Dmesg shows that the disk is recognized and immediately after this two kernel panics occur. It does not matter how the ZFS volume is connected. I tried to connect the same disk as USB and IDE device. NOTE: I'm not shure if it is related to ZFS. I renamed the zfs kernel modules (just to be shure that they can not be loaded). And the panics also occured. It might have to do with the fact that OSX creates GPT (Guid Partition Table) and FBSD can not deal with it? The panics are not written to the filesystem, and currently I've no dump device available that's big enough (4gb ram, 2gb swap). If you need a dump or any further information, let me know - I'll try to get it.
Hi there, I'm the bad guy who created Stefan's panic'ish volume. I've created the ZPool on the USB-disk via: "diskutil partitiondisk /dev/diskX GPTFormat ZFS %noformat% 100%" and "zpool create usbdisk diskXs2". My ZFS implementation was creating a ZPool v6 and I didn't upgrade it to v8. My Mac is running 10.6.2 (Build 10C540, 64bit) with dustin's ZFS-Patches from http://github.com/dustin/mac-zfs Good luck and best wishes, Sebastian
Responsible Changed From-To: freebsd-amd64->freebsd-fs Over to maintainer(s).
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
^Triage: I'm sorry that this PR did not get addressed in a timely fashion. By now, the version that it was created against is long out of support. As well, many newer versions of ZFS have been imported. Please re-open if it is still a problem on a supported version.