From owner-freebsd-fs@FreeBSD.ORG Mon Jun 30 21:40:04 2008 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43A9A106568B for ; Mon, 30 Jun 2008 21:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2DFFE8FC36 for ; Mon, 30 Jun 2008 21:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5ULe4sB067140 for ; Mon, 30 Jun 2008 21:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5ULe4LF067139; Mon, 30 Jun 2008 21:40:04 GMT (envelope-from gnats) Date: Mon, 30 Jun 2008 21:40:04 GMT Message-Id: <200806302140.m5ULe4LF067139@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Joerg Wunsch Cc: Subject: Re: kern/114676: snapshot creation panics: snapacct_ufs2: bad block X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joerg Wunsch List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 21:40:04 -0000 The following reply was made to PR kern/114676; it has been noted by GNATS. From: Joerg Wunsch To: bug-followup@freebsd.org Cc: Subject: Re: kern/114676: snapshot creation panics: snapacct_ufs2: bad block Date: Mon, 30 Jun 2008 22:34:42 +0200 FreeBSD-7-stable is completely unstable for me due to this panic. I used to have regular snapshots enabled on /var and /home. While there has been random (and not quite reproducible) file corruption happened within snapshotted binary files in the past, after upgrading from FreeBSD 6.x to 7-stable, the system went completely unstable due to this panic. It crashes every couple of days now. I have already disabled the regular snapshots, but it's got a tendency for a complete hard lockup during startup after a crash. The only remedy then is to manually fsck everything in single-user mode. Here's the dump information from the recent crash dumps: Dump header from device /dev/ad4s1b Architecture: i386 Architecture Version: 2 Dump Length: 317976576B (303 MB) Blocksize: 512 Dumptime: Wed Jun 25 04:10:25 2008 Hostname: uriah.heep.sax.de Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-STABLE #5: Tue Jun 17 15:06:46 MET DST 2008 r@uriah.heep.sax.de:/usr/obj/usr/src/sys/URIAH Panic String: snapacct_ufs2: bad block Dump Parity: 558154102 Bounds: 42 Dump Status: good Dump header from device /dev/ad4s1b Architecture: i386 Architecture Version: 2 Dump Length: 180707328B (172 MB) Blocksize: 512 Dumptime: Mon Jun 30 22:05:09 2008 Hostname: uriah.heep.sax.de Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-STABLE #6: Mon Jun 30 21:24:35 MET DST 2008 root@uriah.heep.sax.de:/usr/obj/usr/src/sys/URIAH Panic String: snapacct_ufs2: bad block Dump Parity: 859829782 Bounds: 43 Dump Status: good I'm going to avoid /any/ kind of snapshot (even dump -L) now just to get a stable system again (hopefully). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)