From owner-freebsd-current@FreeBSD.ORG  Mon Jun 14 17:11:27 2004
Return-Path: <owner-freebsd-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 B6E2D16A4D4
	for <freebsd-current@freebsd.org>;
	Mon, 14 Jun 2004 17:11:27 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 584D343D4C
	for <freebsd-current@freebsd.org>;
	Mon, 14 Jun 2004 17:11:27 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i5EHABol035584;
	Mon, 14 Jun 2004 13:10:11 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i5EHABFF035581;
	Mon, 14 Jun 2004 13:10:11 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Mon, 14 Jun 2004 13:10:11 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Ronald Klop <ronald-freebsd7@klop.yi.org>
In-Reply-To: <opr9lgi9yam97yfk@outgoing.local>
Message-ID: <Pine.NEB.3.96L.1040614130818.34947A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: FreeBSD-current <freebsd-current@freebsd.org>
Subject: Re: panic: ffs_valloc: dup alloc
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2004 17:11:27 -0000

On Mon, 14 Jun 2004, Ronald Klop wrote:

> I'm getting this panic 'panic: ffs_valloc: dup alloc'.  It happens on
> -CURRENT, since quite some time.  It happens when doing an rsync from a
> remote server to my secondary disk.  (ad2,master on ata1), there is no
> slave on this controller.  And it always happens, so it is very
> repeatable.  Is this probably a hardware failure? Or software? 

"dup alloc" tends to be a common symptom of races or other corruption
(improper zeroing of memory, etc).  One thing I might recommend doing, if
you haven't done it already, is to boot to single-user and do a manual
fsck of the drive experiencing the problem to help identify if on-disk
corruption is the source.  It might well be useful to log the results of
that fsck to a log file (perhaps in an md memory backed file system) to
include in a follow-up if there's anything interesting. 

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Senior Research Scientist, McAfee Research


> 
> $ uname -a
> FreeBSD henk.thuis.klop.ws 5.2-CURRENT FreeBSD 5.2-CURRENT #24: Mon Jun 14  
> 00:25:19 CEST 2004     root@henk.thuis.klop.ws:/usr/obj/usr/src/sys/HENK   
> i386
> 
> A backtrace of the kernel core dump is in the attached gdb.txt.
> My dmesg is also attached.
> 
> Can I provide more info?
> 
> Greetings,
> 
> Ronald.
> 
> PS: Searched the archives and google, but didn't find anything usefull yet.
> 
> -- 
>   Ronald Klop
>   Amsterdam, The Netherlands
>