From owner-freebsd-current@FreeBSD.ORG  Tue Apr  6 15:56:21 2004
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 7B6DB16A4CE
	for <current@freebsd.org>; Tue,  6 Apr 2004 15:56:21 -0700 (PDT)
Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 07F7943D45
	for <current@freebsd.org>; Tue,  6 Apr 2004 15:56:21 -0700 (PDT)
	(envelope-from WillS@housing.ufl.edu)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
x-mimeole: Produced By Microsoft Exchange V6.0.6249.0
Date: Tue, 6 Apr 2004 18:55:24 -0400
Message-ID: <0E972CEE334BFE4291CD07E056C76ED802E8692E@bragi.housing.ufl.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: drive failure, now 'cannot alloc 494581644 bytes for inoinfo'and
	'bad inode number 3556352 to nextinode'
Thread-Index: AcQcKXl8XiM7Ow90Ru+LYOPyCM+/kAAAKpjw
From: "Will Saxon" <WillS@housing.ufl.edu>
To: <current@freebsd.org>
Subject: RE: drive failure, now 'cannot alloc 494581644 bytes for inoinfo'
	and'bad inode number 3556352 to nextinode'
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: Tue, 06 Apr 2004 22:56:21 -0000



> -----Original Message-----
> From: Will Saxon=20
> Sent: Tuesday, April 06, 2004 6:50 PM
> To: current@freebsd.org
> Subject: drive failure, now 'cannot alloc 494581644 bytes for inoinfo'
> and'bad inode number 3556352 to nextinode'
>=20
> At the time of the crash, I was using FreeBSD 5.2.1-RC2,=20
> however I have since updated to 5.2.1-RELEASE-p4. The array=20
> has 1 partition and 2 slices - one 4GB swap slice and 1=20
> 400+GB storage slice. This was being used in a samba pilot=20
> and had the softupdates, suiddir, noexec, nodev and acl=20
> options enabled.
>=20
> Basically, in phase 1 fsck -y complains that it cannot=20
> allocate enough bytes for inoinfo, then there are a bunch of=20
> the following:
>=20
> UNKNOWN FILE TYPE I=3D#######
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>=20
> then finally:
>=20
> fsck_4.2bsd: bad inode number 3556352 to nextinode

Also, dumpfs coredumps (dumpfs /dev/da1s1d) in case that
piques anyone's interest.

-Will