From owner-freebsd-bugs@FreeBSD.ORG  Sat Jul 12 15:15:16 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 53F9337B401; Sat, 12 Jul 2003 15:15:16 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id D982943F75; Sat, 12 Jul 2003 15:15:15 -0700 (PDT)
	(envelope-from kris@FreeBSD.org)
Received: from freefall.freebsd.org (kris@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6CMFFUp016855;
	Sat, 12 Jul 2003 15:15:15 -0700 (PDT)
	(envelope-from kris@freefall.freebsd.org)
Received: (from kris@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6CMFF7C016845;
	Sat, 12 Jul 2003 15:15:15 -0700 (PDT)
Date: Sat, 12 Jul 2003 15:15:15 -0700 (PDT)
From: Kris Kennaway <kris@FreeBSD.org>
Message-Id: <200307122215.h6CMFF7C016845@freefall.freebsd.org>
To: dot@dotat.at, kris@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/35248: panic: ffs_valloc: dup alloc
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jul 2003 22:15:16 -0000
X-List-Received-Date: Sat, 12 Jul 2003 22:15:16 -0000

Synopsis: panic: ffs_valloc: dup alloc

State-Changed-From-To: feedback->closed
State-Changed-By: kris
State-Changed-When: Sat Jul 12 15:13:29 PDT 2003
State-Changed-Why: 
Feedback timeout.  FWIW, I see this panic regularly on
the bento cluster because of hardware failure with the IDE
drives.  Scrubbing the disk with dd if=/dev/zero of=/dev/ad0
periodically causes the drive to remap/reset bad or marginal
sectors and the problem goes way.

http://www.freebsd.org/cgi/query-pr.cgi?pr=35248