From owner-freebsd-current@FreeBSD.ORG  Fri Oct 14 10:32:41 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1C94B1065675
	for <freebsd-current@freebsd.org>; Fri, 14 Oct 2011 10:32:41 +0000 (UTC)
	(envelope-from jonathan.robert.anderson@gmail.com)
Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com
	[209.85.216.54])
	by mx1.freebsd.org (Postfix) with ESMTP id CAF718FC1C
	for <freebsd-current@freebsd.org>; Fri, 14 Oct 2011 10:32:40 +0000 (UTC)
Received: by qadz30 with SMTP id z30so890457qad.13
	for <freebsd-current@freebsd.org>; Fri, 14 Oct 2011 03:32:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	bh=a/ZG0fNmQKDBeGmE59lCx1aGORICm4T5pAperidIDZc=;
	b=FIofAUptPQcD5sWOAvBw2O2sWupEwYKITDOjCk+2kANfl1iKqFwA63cUJrbZC50bgA
	KARconl+1A9rn7A8K9fM3/zHD3pVxEsBtq0GRePdwBjpStQqGkGrYDO+VWouOkZGUj7T
	81Q29Le/mtCzkOj8k/xoabJYjAaCY4pP89NM4=
MIME-Version: 1.0
Received: by 10.182.147.42 with SMTP id th10mr4799361obb.44.1318588359611;
	Fri, 14 Oct 2011 03:32:39 -0700 (PDT)
Sender: jonathan.robert.anderson@gmail.com
Received: by 10.182.188.71 with HTTP; Fri, 14 Oct 2011 03:32:39 -0700 (PDT)
In-Reply-To: <alpine.GSO.1.10.1110061058050.882@multics.mit.edu>
References: <CAMGEAwBECZHcoAcP_D-v-RivaiHJh18OkQu-61WJJQ68+xXWGQ@mail.gmail.com>
	<CAMGEAwAwdu8H50_aD367CM+KKuzYemEWMAubXTmfXBeYmvJRLw@mail.gmail.com>
	<alpine.GSO.1.10.1110061058050.882@multics.mit.edu>
Date: Fri, 14 Oct 2011 11:32:39 +0100
X-Google-Sender-Auth: L6bD9ieU3Ggmf-XiYIeycn6xQeA
Message-ID: <CAMGEAwDrhL0xN-ba+UkxYo7yGCu-ndr=h9RB9LzYewz8JWRo3A@mail.gmail.com>
From: Jonathan Anderson <jonathan@FreeBSD.org>
To: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-current@freebsd.org
Subject: Re: PANIC: "ffs_valloc: dup alloc" on boot
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Fri, 14 Oct 2011 10:32:41 -0000

That's ok, a more aggressive fsck-from-a-rescue-disk strategy managed
to clean things up.


J Anderson

On 6 October 2011 15:58, Benjamin Kaduk <kaduk@mit.edu> wrote:
> On Thu, 6 Oct 2011, Jonathan Anderson wrote:
>
>> On 5 October 2011 23:50, Jonathan Anderson <jonathan@freebsd.org> wrote:
>>>
>>> I was about to upgrade my build VM from BETA2 to BETA3, but I can't
>>> seem to boot BETA2 any more: I get a "ffs_valloc: dup alloc" panic on
>>> boot, every time. fsck runs and says, "ok, I've cleaned things up for
>>> you", but then later on, when trying to update motd, FFS dies.
>>
>> Here are two screenshots: fsck succeeding and the relevant backtrace.
>
> Mailman seems to have stripped them.
>
> -Ben Kaduk
>



-- 
Jonathan Anderson

jonathan@FreeBSD.org
http://freebsd.org/~jonathan/