From owner-freebsd-stable@FreeBSD.ORG  Tue Sep 19 05:46:32 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EC79316A403
	for <freebsd-stable@freebsd.org>; Tue, 19 Sep 2006 05:46:32 +0000 (UTC)
	(envelope-from noctua@bellsouth.net)
Received: from imf16aec.mail.bellsouth.net (imf16aec.mail.bellsouth.net
	[205.152.59.64])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7651343D45
	for <freebsd-stable@freebsd.org>; Tue, 19 Sep 2006 05:46:32 +0000 (GMT)
	(envelope-from noctua@bellsouth.net)
Received: from ibm56aec.bellsouth.net ([65.6.151.211])
	by imf16aec.mail.bellsouth.net with ESMTP id
	<20060919054631.LDSM10168.imf16aec.mail.bellsouth.net@ibm56aec.bellsouth.net>
	for <freebsd-stable@freebsd.org>; Tue, 19 Sep 2006 01:46:31 -0400
Received: from pinbot ([65.6.151.211]) by ibm56aec.bellsouth.net with SMTP
	id <20060919054631.VHQD14125.ibm56aec.bellsouth.net@pinbot>
	for <freebsd-stable@freebsd.org>; Tue, 19 Sep 2006 01:46:31 -0400
Received: by pinbot (sSMTP sendmail emulation); Tue, 19 Sep 2006 01:47:34 -0400
Date: Tue, 19 Sep 2006 01:47:34 -0400
From: noctua@bellsouth.net
To: freebsd-stable@freebsd.org
Message-ID: <20060919054734.GA18613@pinbot.noctuarium.org>
Mail-Followup-To: freebsd-stable@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
Subject: ufs - fsck_ffs problem
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2006 05:46:33 -0000

Hola,

I'm running 6.1, and experiening some problems with my RAID array.  Using a
3ware escalade, some corruption to the file system has occurred during a
power outage.  The raw hardware of the filesystem is fine -- at least as far
as the 3ware device is concerned.

At any rate, I issued:

fsho# fsck_ffs -n -b 160 /dev/da0c
Alternate super block location: 160
** /dev/da0c
** Last Mounted on 
** Phase 1 - Check Blocks and Sizes
fsck_ffs: cannot alloc 2641372856 bytes for inoinfo

I found some code by Einstein: <http://www.atm.tut.fi/list-archive/freebsd-stable-2005/msg04212.html>
which seems to get past the problem.  But, I'm certainly concerned about the
sanctity of my data, and have committed no suggested changes by the program,
as witnessed below:

Alternate super block location: 160
** /dev/da0c (NO WRITE)
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
UNKNOWN FILE TYPE I=2
CLEAR? no

PARTIALLY ALLOCATED INODE I=62
CLEAR? no

PARTIALLY ALLOCATED INODE I=75
CLEAR? no

PARTIALLY ALLOCATED INODE I=110
CLEAR? no

512903222015925405 BAD I=129
2363463046329258390 BAD I=129
-4878472826699975618 BAD I=129
-3101413049108763758 BAD I=129
-4942707920151290579 BAD I=129
8570194651996646049 BAD I=129
2315016788075931432 BAD I=129
-1520079671300232671 BAD I=129
-8795335986215733707 BAD I=129
-4534688454961916277 BAD I=129
5406555421949755135 BAD I=129
EXCESSIVE BAD BLKS I=129
CONTINUE? yes

PARTIALLY TRUNCATED INODE I=130
SALVAGE? no

.....  and this will go on forever, finding billions of problems.

I'm at a loss.  The file system cannot be that corrupt.  Any advice?