From owner-freebsd-current@FreeBSD.ORG  Sun Feb 27 22:39:37 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 3190B16A4CE; Sun, 27 Feb 2005 22:39:37 +0000 (GMT)
Received: from obsecurity.dyndns.org
	(CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DD89943D1F; Sun, 27 Feb 2005 22:39:36 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 03AD551480; Sun, 27 Feb 2005 14:39:35 -0800 (PST)
Date: Sun, 27 Feb 2005 14:39:35 -0800
From: Kris Kennaway <kris@obsecurity.org>
To: Don Lewis <truckman@FreeBSD.org>
Message-ID: <20050227223935.GA48482@xor.obsecurity.org>
References: <20050227050523.GA92300@xor.obsecurity.org>
	<200502271024.j1RAO6jC010109@gw.catspoiler.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe"
Content-Disposition: inline
In-Reply-To: <200502271024.j1RAO6jC010109@gw.catspoiler.org>
User-Agent: Mutt/1.4.2.1i
cc: current@FreeBSD.org
cc: kris@obsecurity.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 22:39:37 -0000


--G4iJoqBmSsgzjUCe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Feb 27, 2005 at 02:24:06AM -0800, Don Lewis wrote:
> On 26 Feb, Kris Kennaway wrote:
> > A recent panic left my FS with some serious corruption, which fsck is
> > unable to repair:
> >=20
> > # 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
> >=20
> > (same holds for any superblock I've tried).
> >=20
> > How can I recover from this, short of running newfs?
>=20
> 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.

I needed to get the machine back up and running so I mounted /var r/o,
copied across data without incident and newfs'ed the filesystem.

Kris


--G4iJoqBmSsgzjUCe
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCIkwnWry0BWjoQKURAoFuAKDE/b27EsPSjd+QqZ5y/B57W1gtSACgraeZ
GK4F6rlBvyitriJ1+It1ljI=
=UXox
-----END PGP SIGNATURE-----

--G4iJoqBmSsgzjUCe--