From owner-freebsd-current@FreeBSD.ORG  Sun Feb 27 10:24:15 2005
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 2264516A4DC
	for <current@FreeBSD.org>; Sun, 27 Feb 2005 10:24:15 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BCFDC43D5A
	for <current@FreeBSD.org>; Sun, 27 Feb 2005 10:24:14 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j1RAO6jC010109;
	Sun, 27 Feb 2005 02:24:11 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200502271024.j1RAO6jC010109@gw.catspoiler.org>
Date: Sun, 27 Feb 2005 02:24:06 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: kris@obsecurity.org
In-Reply-To: <20050227050523.GA92300@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: current@FreeBSD.org
Subject: Re: fsck_ufs: cannot alloc 3166749884 bytes for inoinfo
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: Sun, 27 Feb 2005 10:24:15 -0000

On 26 Feb, Kris Kennaway wrote:
> A recent panic left my FS with some serious corruption, which fsck is
> unable to repair:
> 
> # fsck_ufs -b 376512 -fy /var
> Alternate super block location: 376512
> ** /dev/twed0s1e
> ** Last Mounted on
> ** Phase 1 - Check Blocks and Sizes
> fsck_ufs: cannot alloc 3166749884 bytes for inoinfo
> 
> (same holds for any superblock I've tried).
> 
> How can I recover from this, short of running newfs?

What does dumpfs say about the contents of the superblock?  For some
reason fsck thinks it needs to allocate space to hold the information
about 791687471 in one cylinder group, which seems a bit unlikely.