From owner-freebsd-current@FreeBSD.ORG Sat Jul 28 16:49:24 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3997D16A419 for ; Sat, 28 Jul 2007 16:49:24 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from proxy3.bredband.net (proxy3.bredband.net [195.54.101.73]) by mx1.freebsd.org (Postfix) with ESMTP id F0CF813C45D for ; Sat, 28 Jul 2007 16:49:23 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from prometheus.scode.org (85.229.22.84) by proxy3.bredband.net (7.3.127) id 46A8FA4C00088783 for current@freebsd.org; Sat, 28 Jul 2007 18:28:28 +0200 Received: from localhost (localhost [127.0.0.1]) by prometheus.scode.org (Postfix) with ESMTP id C321D1CC8E for ; Sat, 28 Jul 2007 20:28:37 +0200 (CEST) From: Peter Schuller To: current@freebsd.org Date: Sat, 28 Jul 2007 20:28:36 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200707282028.37102.peter.schuller@infidyne.com> Cc: Subject: (ZFS?): panic: lockmgr: locking against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2007 16:49:24 -0000 Hello, I have a machine with root on ZFS and /boot on gmirror. Version is 7-CURRENT from about a week ago or so (can't check since system won't boot). After a certain sequence of events that I will describe below, I now get this on boot (typed manually, so there may be some mistakes): Trying to mount root from zfs:tank/root panic: lockmgr: locking against myself cpuid = 0 KBD: enter: panic [thread pid 1 tid 100002 ] Stopped at kbd_enter+0x31: leave db>bt kbd_enter() at kbd_enter+0x31 panic() at panic+0x173 _lockmgr() at _lockmgr+0x085a VOP_LOCK1_APV() at VOP_LOCK1_APV+0x46 _vn_lock() at _vn_lock+0x83 vrele() at vrele+0xf5 mountcheckdirs() at mountcheckdirs+0x1e8 vfs_donmount() at vfs_donmount+0x111c kernel_mount() at kernel_mount+0x88 kernel_vmount() at kernel_vmoun+0xcb vfs_mountroot_try() at vfs_mountroot_try+0x10c vfs_mountroot() at vfs_mountroot+0x324 start_init() at start_init+0x4d fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffffac357d30, rbp = 0 --- This is on a Dell 2950, with two SATA drives exposed as individual non-redundant volumes through the PERC 5/i controller (mfi driver). The sequence of events were: (1) Boot the system. (2) Yank one of the drives live; watch errors flash by, zfs detecting the corruption of one of the drives. (3) Reboot with the drive missing, confirming booting still works (I am *pretty* sure I did this). (4) Shutdown, insert drive again, enable it in RAID controller config, and boot. (5) Gmirror refuses to use the swapped drive because it is "broken" (not sure why this happened; I was assuming it would detect it as out of date and rebuild). I manually forget and re-insert the drive. (6) Meanwhile, ZFS has resilvered and is reporting some checksum mismatches. I scrub the pool and heal some more checksum mismatches (corruption/bitflips on hotswap is consistent with some other experience with a Marvell controller and attempted hotswapping). Second scrub completes without errors. (7) All is fine. I shut the machine down physically, remove one drive, and try to boot for the purpose of testing this particular failure mode. (8) I now get the above panic on trying to mount root. (9) Shutdown, re-insert drive again per above, and try to boot. Still the same panic. Both drives are now being detected in the gmirror though. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org