Crash under new Mavericks upgrade

[Alex Wasserman]

Hey all,

3 mins after boot, I get a crash...

Any idea why?

Thanks,

Alex

[Alex Wasserman]

Had to switch to using my iPad. I get a freeze shortly after boot after a mavericks upgrade. The pool loads and is usable, but Console has the crash logs attached.

Any idea of the root cause? I'm using a freshly built and installed drivers, pulled from git, built and installed in s/l/e,

Thanks,

Alex

[ilov...@icloud.com]

Those crash logs look irrelevant to the freeze because they would have come from manual invocations of the /usr/local/sbin/zfs command and a crash of just that userland command (like when Safari crashes so that you have to reopen it) as opposed to something happening on its own. Do the time stamps actually match up with when the freezes occur?

How are you importing your pools? What version are the pools? What version are the file systems? Do you have any pools created by ZFS-OSX? Does it happen with them without other pools imported?

What do you mean by freeze? Is the system responsive to an attempt to login via ssh or is it totally dead? Does the caps lock key work? Are there kernel panic logs in /Library/Logs/DiagnosticReports with time stamps matching the freeze? Do you know what you were doing at the time it froze up?

Did you rebuild after upgrading to Mavericks? Are you sure this wasn't happening before the upgrade? What version of Xcode are you using?

[Jorgen Lundman]

ilov...@icloud.com wrote:
> Those crash logs look irrelevant to the freeze because they would have
> come from manual invocations of the /usr/local/sbin/zfs command and a
> crash of just that userland command (like when Safari crashes so that
> you have to reopen it) as opposed to something happening on its own.
> Do the time stamps actually match up with when the freezes occur?

Userland crash is from

return (zfs_standard_error(hdl, errno,
dgettext(TEXT_DOMAIN, "failed to read "
"pool configuration")));

but that isn't really the issue. What runs this command?

[ilov...@icloud.com]

The error originates here I believe:

https://github.com/zfs-osx/zfs/blob/cad998d9513453c65b63c1154f45c042c4b32a04/module/zfs/zfs_ioctl.c#L1261

[ilov...@icloud.com]

The error is actually just the error you get whenever you run the zfs command without sudo.

[Alex Wasserman]

Hmm, damn. Not sure what was triggering that as I hadn't done it myself.

But, looks like it was just coincidental timing. Something loading on boot and running a zpool, right when the system hung.

Switching to console mode got the kernel panic to show, and looks like the error was on a different kext, the NullCPUPowerManagement one, so ZFS is in the clear.

Thanks for looking at this. Yes, I had done a fresh build and install, and yes, the crash log was from the same time, but with a crash 2 mins after boot, a lot of stuff was running then.

[ozialien]

Could it be iokit mass storage instance holding a mass storage device in cache with a zpool reference?d

Even though fs's are BSD monolithic in OSX the physical media device is all IOKit.   AppleFilesystem.kext seems just to be a post device discovery boot loading Event.  

I am not sure of this but it's been my experience that the iokit discovery event for a zpool device triggers a import     

Me
Sent from my iPhone

--
See http://MacZFS.org/ for more information on this project.
---
You received this message because you are subscribed to the Google Groups "MacZFS-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maczfs-devel...@googlegroups.com.
Visit this group at http://groups.google.com/group/maczfs-devel.

[Aaron Stone]

Hi Alex,

I had a similar situation after I upgraded to Mavericks and I solved it by compiling zfs and spl under Mavericks.

Aaron

[ilov...@icloud.com]

These are the guidelines for what should be built where in the Brave New Mavericks World:

http://i.imgur.com/3bfdvus.png

That's from page 171 of What’s New in Kext Development:

https://developer.apple.com/wwdc/videos/