Kernel panic in (77.0.9 experimental) (applies to deprecated build)

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. See issue 67
2. Upgrade to 77.0.9
3. Use machine

What is the expected output? What do you see instead?
System not to kernel panic

What version of the product are you using? On what operating system?
77.0.9 on 10.6.5

Please provide any additional information below.

Original issue reported on code.google.com by patri...@gmail.com on 20 Jan 2011 at 10:56

Attachments:

GoogleCodeExporter commented 8 years ago

Can you run the "panic-decode" script to understand where the panic is coming 
from? The details are on the wiki.

Original comment by alex.ble...@gmail.com on 20 Jan 2011 at 11:42

GoogleCodeExporter commented 8 years ago

Hope this helps

Original comment by patr...@m.ac.nz on 21 Jan 2011 at 8:32

Attachments:

panic_20110121191952.txt

GoogleCodeExporter commented 8 years ago

Thanks, I'll take a look

Original comment by alex.ble...@gmail.com on 21 Jan 2011 at 9:59

Changed title: Kernel panic in 77.0.9

GoogleCodeExporter commented 8 years ago

Also, just in case it's not obvious from my steps - I didn't upgrade the on 
disk format, and the current output of zpool status is:

patrick@cole:/Users/patrick$ zpool status
  pool: Apathy
 state: ONLINE
status: The pool is formatted using an older on-disk format.  The pool can
    still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
    pool will no longer be accessible on older software versions.
 scrub: none requested
config:

    NAME         STATE     READ WRITE CKSUM
    Apathy       ONLINE       0     0     0
      raidz1     ONLINE       0     0     0
        disk5s2  ONLINE       0     0     0
        disk6s2  ONLINE       0     0     0
        disk4s2  ONLINE       0     0     0
      raidz1     ONLINE       0     0     0
        disk2s2  ONLINE       0     0     0
        disk1s2  ONLINE       0     0     0
        disk3s2  ONLINE       0     0     0

errors: No known data errors

Original comment by patri...@gmail.com on 22 Jan 2011 at 6:57

GoogleCodeExporter commented 8 years ago

Using 77.0.9 on 10.6.6 (i386), I've had a couple of panics. I've had panics 
before (I believe with older versions of OS X/mac-zfs), but I only now found 
the panic-decode script.

I'm currently running a zpool scrub using VirtualBox / Solaris 11 (snv_151a) on 
my OS X host to see if there's anything actually wrong with the drive. (The 
system froze once during this scrub, but thankfully when I imported a second 
time, solaris resumed the scrub so I should be able to eventually get results).

  pool: pool
 state: ONLINE
status: The pool is formatted using an older on-disk format.  The pool can
    still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
    pool will no longer be accessible on older software versions.
 scan: scrub in progress since Wed Feb  2 16:26:57 2011
    95.0G scanned out of 431G at 6.69M/s, 14h16m to go
    0 repaired, 22.05% done
config:

    NAME        STATE     READ WRITE CKSUM
    pool        ONLINE       0     0     0
      c8t1d0p0  ONLINE       0     0     0

errors: No known data errors

Original comment by timel...@gmail.com on 3 Feb 2011 at 2:56

Attachments:

Kernel_2011-02-01-154435.panic

GoogleCodeExporter commented 8 years ago

scrub finished, no errors found

Original comment by timel...@gmail.com on 4 Feb 2011 at 1:42

GoogleCodeExporter commented 8 years ago

At least one path is hitting this part, in 'zfs_context', where it's obviously 
attempting to double-lock something during unmount. I suspect it may be related.

    if (mp->m_owner == current_thread())
        panic("mutex_enter: locking against myself!");

Original comment by alex.ble...@gmail.com on 27 Feb 2011 at 1:13

GoogleCodeExporter commented 8 years ago

Call path leading up to this event:

0x4631cf75 in mutex_enter (mp=0x3c) at 
/Users/alex/Projects/MacZFS/usr/src/maczfs/kernel/zfs_context.c:447
447     if (mp->m_owner == current_thread())
(gdb) bt
#0  0x4631cf75 in mutex_enter (mp=0x3c) at 
/Users/alex/Projects/MacZFS/usr/src/maczfs/kernel/zfs_context.c:447
#1  0x4628a7f4 in dbuf_rele (db=0x0, tag=0x0) at 
/Users/alex/Projects/MacZFS/usr/src/uts/common/fs/zfs/dbuf.c:1709
#2  0x4631cdea in dmu_buf_rele (db=0x0, tag=0x0) at 
/Users/alex/Projects/MacZFS/usr/src/maczfs/kernel/zfs_context.c:317
#3  0x462f41e7 in zfsvfs_teardown (zfsvfs=0x4f15800, unmounting=1) at 
/Users/alex/Projects/MacZFS/usr/src/uts/common/fs/zfs/zfs_vfsops.c:1885
#4  0x462f43db in zfs_vfs_unmount (mp=0xa9a7520, mntflags=0, context=0x5b37b24) 
at /Users/alex/Projects/MacZFS/usr/src/uts/common/fs/zfs/zfs_vfsops.c:2047
#5  0x002eecab in dounmount (mp=0xa9a7520, flags=0, withref=1, ctx=0x5b37b24) 
at /SourceCache/xnu/xnu-1504.9.17/bsd/vfs/vfs_syscalls.c:1598

Original comment by alex.ble...@gmail.com on 27 Feb 2011 at 1:14

GoogleCodeExporter commented 8 years ago

Original comment by alex.ble...@gmail.com on 5 Mar 2011 at 10:51

Changed title: Kernel panic in (77.0.9 experimental)

GoogleCodeExporter commented 8 years ago

Original comment by alex.ble...@gmail.com on 19 Mar 2011 at 8:32

Changed title: Kernel panic in (77.0.9 experimental) (applies to deprecated build)
Changed state: WontFix

gmzang / maczfs

Kernel panic in (77.0.9 experimental) (applies to deprecated build) #75