From j@uriah.heep.sax.de  Mon Jun 30 20:34:44 2008
Return-Path: <j@uriah.heep.sax.de>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0C3441065671
	for <freebsd-gnats-submit@freebsd.org>; Mon, 30 Jun 2008 20:34:44 +0000 (UTC)
	(envelope-from j@uriah.heep.sax.de)
Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9])
	by mx1.freebsd.org (Postfix) with ESMTP id A7A6C8FC13
	for <freebsd-gnats-submit@freebsd.org>; Mon, 30 Jun 2008 20:34:43 +0000 (UTC)
	(envelope-from j@uriah.heep.sax.de)
Received: by uriah.heep.sax.de (Postfix, from userid 107)
	id 942845F5; Mon, 30 Jun 2008 22:34:42 +0200 (MET DST)
Message-Id: <20080630203442.GA1469@uriah.heep.sax.de>
Date: Mon, 30 Jun 2008 22:34:42 +0200
From: Joerg Wunsch <j@uriah.heep.sax.de>
Reply-To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
To: freebsd-gnats-submit@freebsd.org
Subject: [kern/114676] snapshot creation panics: snapacct_ufs2: bad block

>Number:         125127
>Category:       kern
>Synopsis:       [kern/114676] snapshot creation panics: snapacct_ufs2: bad block
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gavin
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jun 30 20:40:03 UTC 2008
>Closed-Date:    Mon Jun 30 21:33:18 UTC 2008
>Last-Modified:  Mon Jun 30 21:33:18 UTC 2008
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 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. ;-)
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: gavin 
State-Changed-When: Mon Jun 30 21:32:33 UTC 2008 
State-Changed-Why:  
Misfiled followup to kern/114676, content migrated 


Responsible-Changed-From-To: gnats-admin->gavin 
Responsible-Changed-By: gavin 
Responsible-Changed-When: Mon Jun 30 21:32:33 UTC 2008 
Responsible-Changed-Why:  


http://www.freebsd.org/cgi/query-pr.cgi?pr=125127 
>Unformatted:
