From owner-freebsd-current@FreeBSD.ORG Tue Apr 6 15:51:20 2004 Return-Path: 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 55E3316A4CE for ; Tue, 6 Apr 2004 15:51:20 -0700 (PDT) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F77243D53 for ; Tue, 6 Apr 2004 15:51:19 -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:49:53 -0400 Message-ID: <0E972CEE334BFE4291CD07E056C76ED8CBBEE3@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+/kA== From: "Will Saxon" To: Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Apr 2004 22:51:20 -0000 Hello, Today, I had a drive fail in a large raid 5 array hosted off of a ciss = device. I removed the bad drive but before I was able to get another = drive swapped in, another drive seemed to just lose power and then the = system panicked. =20 I swapped in a spare drive and restarted the system. The controller said = the array was 'ok' and would recover. However, FreeBSD is having a hard = time fsck'ing the partition. At the time of the crash, I was using FreeBSD 5.2.1-RC2, however I have = since updated to 5.2.1-RELEASE-p4. The array has 1 partition and 2 = slices - one 4GB swap slice and 1 400+GB storage slice. This was being = used in a samba pilot and had the softupdates, suiddir, noexec, nodev = and acl options enabled. Basically, in phase 1 fsck -y complains that it cannot allocate enough = bytes for inoinfo, then there are a bunch of the following: UNKNOWN FILE TYPE I=3D####### UNEXPECTED SOFT UPDATE INCONSISTENCY then finally: fsck_4.2bsd: bad inode number 3556352 to nextinode Any ideas? -Will _____________________________________________ Will Saxon Systems Programmer - Network Services Department of Housing and Residence Education University of Florida Email: wills@housing.ufl.edu Phone: (352) 392-2171 x10148