From owner-freebsd-fs@FreeBSD.ORG  Mon Nov 24 03:37:36 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A622F738;
 Mon, 24 Nov 2014 03:37:36 +0000 (UTC)
Received: from chez.mckusick.com (chez.mckusick.com
 [IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8AC74F57;
 Mon, 24 Nov 2014 03:37:36 +0000 (UTC)
Received: from chez.mckusick.com (localhost [127.0.0.1])
 by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id sAO3bJIA076312;
 Sun, 23 Nov 2014 19:37:19 -0800 (PST)
 (envelope-from mckusick@chez.mckusick.com)
Message-Id: <201411240337.sAO3bJIA076312@chez.mckusick.com>
To: lev@freebsd.org
Subject: Re: FreeBSD 10 panic with "ffs_valloc: dup alloc" 
In-reply-to: <54724D8C.3030100@FreeBSD.org> 
Date: Sun, 23 Nov 2014 19:37:19 -0800
From: Kirk McKusick <mckusick@mckusick.com>
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Nov 2014 03:37:36 -0000

> Date: Mon, 24 Nov 2014 00:11:40 +0300
> From: Lev Serebryakov <lev@freebsd.org>
> To: freebsd-fs@freebsd.org
> Subject: Re: FreeBSD 10 panic with "ffs_valloc: dup alloc"
> 
> On 23.11.2014 22:59, Lev Serebryakov wrote:
> 
>> Filesystem in question is clean after panic reboot (!) SU and
>> "native" journal are used. Memory check is Ok. System is amd64,
>> r269936. What could I add to this information to help track & fix
>> this bug?
>  Ok, I could reproduce it. It is triggered by "svnsync" of FreeBSD
> "base" repository. 3 times in a row.
> 
> -- 
> // Lev Serebryakov AKA Black Lion

I don't know what you mean by "native" journal. Is this SUJ or is
it the journal GEOM layer?

In either case, you should take the system down to single user.
Run fsck over the filesystem in question. It will most likely
find something wrong and fix it. After that the problem will be
gone. The problem with any type of journalling is that if a
filesystem error creeps in either because of a write error or
a lying disk (e.g., it says that it did the write, but in fact
the write was lost when the power failed), then the journal does
not know about the error and the only way to fix it is to run a
full filesystem check.

	Kirk McKusick