From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 09:31:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDCD537B401 for ; Sun, 6 Jul 2003 09:31:36 -0700 (PDT) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86E7B44003 for ; Sun, 6 Jul 2003 09:31:35 -0700 (PDT) (envelope-from bruce@cran.org.uk) Received: from buffy.brucec.backnet ([82.41.200.71]) by smtp-out4.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.5329); Sun, 6 Jul 2003 17:31:33 +0100 Received: from buffy.brucec.backnet (localhost.brucec.backnet [127.0.0.1]) by buffy.brucec.backnet (8.12.8p1/8.12.8) with ESMTP id h66GVgLX056993 for ; Sun, 6 Jul 2003 17:31:42 +0100 (BST) (envelope-from bruce@buffy.brucec.backnet) Received: (from bruce@localhost) by buffy.brucec.backnet (8.12.8p1/8.12.8/Submit) id h66GVgtN056992 for current@freebsd.org; Sun, 6 Jul 2003 17:31:42 +0100 (BST) Date: Sun, 6 Jul 2003 17:31:42 +0100 From: Bruce Cran To: current@freebsd.org Message-ID: <20030706163142.GA56957@buffy.brucec.backnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i X-OriginalArrivalTime: 06 Jul 2003 16:31:33.0914 (UTC) FILETIME=[102397A0:01C343DC] Subject: ffs_copyonwrite: locking against myself - snapshot related panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sun, 06 Jul 2003 16:31:37 -0000 I created snapshots of /var, /, /tmp and /usr, and then continued to use the system normally, after beginning to move one of the snapshots across to an nfs directory, then cancelling the move. When I later came to install lftp from /usr/ports/ftp/lftp, I had the following panic: ffs_copyonwrite: locking against myself since a debug kernel wasn't built, I rebooted, fsck'd the filesystems and rebuilt the kernel. I then proceeded to trigger the panic again by running 'make install' in /usr/ports/ftp/lftp, and got the following trace: Debugger panic lockmgr BUF_TIMELOCK getblk breadn bread ffs_alloccg ffs_hashalloc ffs_alloc ffs_balloc_ufs2 ffs_copyonwrite spec_xstrategy spec_specstrategy spec_vnoperate bwrite bawrite ffs_nodealloccg ffs_hashalloc ffs_valloc ufs_makeinode ufs_create ufs_vnoperate VOP_CREATE vn_open_cred vn_open kern_open open syscall Xint0x80_syscall syscall(5, FreeBSD ELF32, open) I can trigger this on demand, whether the 'nvidia' module is loaded or not. All my slices are UFS2, and have been fsck'd in single-user mode. The second panic I had generated messages about recovering errors for about 30 seconds when I fsck'd /usr, so I don't know what kind of state it's now in. The panic seems to have disappeared after I deleted the snapshot files. Are snapshots supposed to be able to be moved/copied around like images - or are they part of the 'real' filesystem, and so have to be treated carefully? -- Bruce Cran