Re: [zfs-discuss] Kernel Panic

[Chris Gerhard]

Richard Elling wrote:

Chris Gerhard wrote:

My home server running snv_94 is tipping with the same assertion when someone list a particular file:

Failed assertions indicate software bugs.  Please file one.
http://en.wikipedia.org/wiki/Assertion_(computing)

If it not fixed then I will file a new bug

--chris

A colleague pointed out that it is an exact match for bug 6746456 so I will upgrade to a later build and check that out. Alas in the mean time the power supply on the system has failed to I can't check this immediately.

-- richard

::status

Loading modules: [ unix genunix specfs dtrace cpu.generic cpu_ms.AuthenticAMD.15 uppc pcplusmp scsi_vhci ufs md ip hook neti sctp arp usba qlc fctl nca lofs zfs audiosup sd cpc random crypto fcip fcp smbsrv nfs logindmux ptm sppp nsctl sdbc sv ii rdc nsmb ipc mpt emlxs ]

::status

debugging crash dump vmcore.17 (64-bit) from pearson
operating system: 5.11 snv_94 (i86pc)

on/fs/zfs/zfs_fuid.c, line: 116
dump content: kernel pages only

panic message: assertion failed: 0 == dmu_bonus_hold(os, fuid_obj, FTAG, &db), file: ../../comm

$c

vpanic()
assfail+0x7e(fffffffff83e3a10, fffffffff83e39f0, 74)

zfs_fuid_init+0xf8(ffffff025a231e40, 0)
zfs_fuid_find_by_idx+0x3f(ffffff025a231e40, 40100)

zfs_zaccess+0x114(ffffff02bc62f4b0, 20000, 0, 0, ffffff02672d0638)
zfs_getacl+0x4c(ffffff02bc62f4b0, ffffff000cfcadd0, 0, ffffff02672d0638)

cacl+0x5ae(6, 0, 0, ffffff02bf7f9740, ffffff000cfcae9c)
acl+0x8d(80665d2, 6, 0, 0)
sys_syscall32+0x101()

zfs_fuid_table_load+0x1ed(ffffff025a1c2448, 0, ffffff025a231e88, ffffff025a231eb0) zfs_fuid_map_id+0x3f(ffffff025a231e40, 4010020c00001, ffffff02672d0638, 2) zfs_zaccess_common+0x246(ffffff02bc62f4b0, 20000, ffffff000cfcabd0, ffffff000cfcabd4, 0, ffffff02672d0638) zfs_getsecattr+0x81(ffffff02bf7f9740, ffffff000cfcadd0, 0, ffffff02672d0638, 0) fop_getsecattr+0x8f(ffffff02bf7f9740, ffffff000cfcadd0, 0, ffffff02672d0638, 0)

ffffff02bf7f9740::print vnode_t

{
    v_lock = {
        _opaque = [ 0 ]
    }
    v_flag = 0x10000
    v_count = 0x2
    v_data = 0xffffff02bc62f4b0
    v_vfsp = 0xffffff025a0055d0
    v_stream = 0
    v_type = 1 (VREG)
    v_rdev = 0xffffffffffffffff
    v_vfsmountedhere = 0
    v_op = 0xffffff02520d2200
    v_pages = 0
    v_filocks = 0
    v_shrlocks = 0
    v_nbllock = {
        _opaque = [ 0 ]
    }
    v_cv = {
        _opaque = 0
    }
    v_locality = 0

    v_rdcnt = 0
    v_wrcnt = 0
    v_mmap_read = 0
    v_mmap_write = 0
    v_mpssdata = 0
    v_fopdata = 0
    v_vsd = 0
    v_xattrdir = 0
    v_count_dnlc = 0x1
}



Need to investigate this further when I get home

v_femhead = 0 v_path = 0xffffff02859d99c8 "/tank/fs/shared/pics/MY_Pictures/SMOV0022.AVI" An ls -l of "/tank/fs/shared/pics/MY_Pictures/SMOV0022.AVI" results in the system crashing.

--
Chris Gerhard.                                         __o __o __o
Systems TSC Chief Technologist                        _`\<,`\<,`\<,_
Sun Microsystems Limited                             (*)/---/---/ (*)
Phone: +44 (0) 1252 426033 (ext 26033) http://blogs.sun.com/chrisg

smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss