From owner-freebsd-fs@FreeBSD.ORG  Wed Feb 10 00:46:33 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 28BE4106568D;
	Wed, 10 Feb 2010 00:46:33 +0000 (UTC)
	(envelope-from mckusick@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 00A328FC08;
	Wed, 10 Feb 2010 00:46:33 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o1A0kWIP072503;
	Wed, 10 Feb 2010 00:46:32 GMT
	(envelope-from mckusick@freefall.freebsd.org)
Received: (from mckusick@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1A0kWjK072499;
	Wed, 10 Feb 2010 00:46:32 GMT (envelope-from mckusick)
Date: Wed, 10 Feb 2010 00:46:32 GMT
Message-Id: <201002100046.o1A0kWjK072499@freefall.freebsd.org>
To: mckusick@FreeBSD.org, freebsd-fs@FreeBSD.org, mckusick@FreeBSD.org
From: mckusick@FreeBSD.org
Cc: 
Subject: Re: kern/133980: [panic] [ffs] panic: ffs_valloc: dup alloc
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Wed, 10 Feb 2010 00:46:33 -0000

Synopsis: [panic] [ffs] panic: ffs_valloc: dup alloc

Responsible-Changed-From-To: freebsd-fs->mckusick
Responsible-Changed-By: mckusick
Responsible-Changed-When: Wed Feb 10 00:43:46 UTC 2010
Responsible-Changed-Why: 
I will take responsibility for this one.

It will require a change in the kernel to properly handle
inode numbers as unsigned.

It will also require a change to newfs to ensure that a
filesystem allocates no more than 2^32 inodes.

Stay tuned for these patches.

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