From owner-freebsd-fs@FreeBSD.ORG Thu Jul 23 08:22:41 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 092B3106564A; Thu, 23 Jul 2009 08:22:41 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id B7A998FC1B; Thu, 23 Jul 2009 08:22:40 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:47556 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.69) (envelope-from ) id 1MTtZD-0002fx-63; Thu, 23 Jul 2009 10:22:21 +0200 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id 838401696A2; Thu, 23 Jul 2009 10:22:15 +0200 (CEST) Message-Id: From: Thomas Backman To: bug-followup@FreeBSD.org, freebsd@r.zeeb.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Thu, 23 Jul 2009 10:22:13 +0200 X-Mailer: Apple Mail (2.935.3) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1MTtZD-0002fx-63. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MTtZD-0002fx-63 a27d59751262fe8beaa58b7e258a33e4 Cc: freebsd-fs@freebsd.org, FreeBSD current Subject: Re: kern/132337: [zfs] [panic] kernel panic in zfs_fuid_create_cred X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2009 08:22:41 -0000 Hey all, Unfortunately, this PR appears to still be unfixed. Is anyone looking at this? I tried to set up a diskless client over NFS yesterday, running ZFS on /, and ran in to this panic (exact same backtrace as the PR (see bottom the this mail)) a lot of times. In the end, I created a ZVOL with UFS on it, and the panics disappeared as expected - since it no longer has to work directly with files on a ZFS *filesystem*. It seems to be pretty easy to trigger, as I couldn't finish the boot process on the diskless client more than once until I went with UFS. Since then I've gotten 0 panics. FWIW, my /etc/exports (I know now R/W NFS root isn't a good idea, but it might be relevant): /diskless -maproot=0 -alldirs 192.168.1.6 Regards, Thomas Backtrace: panic: zfs_fuid_create_cred cpuid = x KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x182 zfs_fuid_create_cred() at zfs_fuid_create_cred+0x56 zfs_perm_init() at zfs_perm_init+0x84 zfs_mknode() at zfs_mknode+0x24e zfs_freebsd_create() at zfs_freebsd_create+0x617 VOP_CREATE_APV() at VOP_CREATE_APV+0xb3 nfsrv_create() at nfsrv_create+0x909 nfssvc_program() at nfssvc_program+0x1a1 svc_run_internal() at svc_run_internal+0x62b svc_thread_start() at svc_thread_start+0xb fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe