From owner-freebsd-current@FreeBSD.ORG Sun Feb 26 01:28:32 2006 Return-Path: X-Original-To: current@freebsd.org 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 5FF7616A420 for ; Sun, 26 Feb 2006 01:28:32 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail22.syd.optusnet.com.au (mail22.syd.optusnet.com.au [211.29.133.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id B867043D45 for ; Sun, 26 Feb 2006 01:28:31 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail22.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k1Q1STa4013128 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 26 Feb 2006 12:28:29 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k1Q1STcA007937 for ; Sun, 26 Feb 2006 12:28:29 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k1Q1SSSQ007936 for current@freebsd.org; Sun, 26 Feb 2006 12:28:29 +1100 (EST) (envelope-from peter) Date: Sun, 26 Feb 2006 12:28:28 +1100 From: Peter Jeremy To: current@freebsd.org Message-ID: <20060226012828.GC707@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: Subject: "fsck -fB" panics: snapacct_ufs2: bad block 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: Sun, 26 Feb 2006 01:28:32 -0000 I noticed that my system hadn't freed up space in / after I accidently filled it a few days ago. "fsck -n" reported a number of unreferenced files that lsof reported were not in use by any processes (I've reported this problem previously). My -current is about 6 weeks old but I don't recall seeing any commits that might affect this. I decided to see if I could get a background fsck to clean up the problem without necessitating a reboot but "fsck -fB /" just panic'd: panic: snapacct_ufs2: bad block KDB: stack backtrace: kdb_backtrace(c06e3fdb,c074b340,c06f4489,d74e7338,100) at kdb_backtrace+0x2e panic(c06f4489,0,800,0,c32a0d80) at panic+0xb7 snapacct_ufs2(c509ab2c,c5aa95e0,c5aa9780,cdd43000,180c) at snapacct_ufs2+0x153 fullacct_ufs2(c509ab2c,c5aa9000,c5aa9780,cdd43000,180c) at fullacct_ufs2+0x44 indiracct_ufs2(c509ab2c,c46a2e38,0,9e68,0) at indiracct_ufs2+0x239 indiracct_ufs2(c509ab2c,c46a2e38,0,9de8,0) at indiracct_ufs2+0x32b expunge_ufs2(c509ab2c,c52f0738,cdd43000,c0626fe0,1) at expunge_ufs2+0x54a ffs_snapshot(c367f000,c4c844a0,d74e7940,6c,c3af5000) at ffs_snapshot+0x18dd ffs_mount(c367f000,c3af5000,c06ecd82,2f9,d74e7a30) at ffs_mount+0xc91 vfs_domount(c3af5000,c36847c0,c3684800,1211300,c35acca0) at vfs_domount+0x5da vfs_donmount(c3af5000,1211300,d74e7b98,c3ddd880,e) at vfs_donmount+0x522 kernel_mount(c48bc1e0,1211300,d74e7bdc,6c,805bb00) at kernel_mount+0x7e ffs_cmount(c48bc1e0,bfbfeb30,1211300,c3af5000,c0736ac0) at ffs_cmount+0x84 mount(c3af5000,d74e7d04,c06ffc05,3ea,c37a5318) at mount+0x1d6 syscall(3b,3b,3b,0,200000) at syscall+0x2f3 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (21, FreeBSD ELF32, mount), eip = 0x280deed7, esp = 0xbfbfea3c, ebp = 0xbfbfebb8 --- KDB: enter: panic I haven't investigated yet but I've got a crash dump if anyone wants to suggest places to look. -- Peter Jeremy