From owner-freebsd-isp@FreeBSD.ORG Tue Jun 6 12:50:43 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEE5616A67C for ; Tue, 6 Jun 2006 12:50:43 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 750C443D46 for ; Tue, 6 Jun 2006 12:50:42 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from webmail.centtech.com (mailbox.centtech.com [10.20.0.15]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k56CofRM094539; Tue, 6 Jun 2006 07:50:42 -0500 (CDT) (envelope-from anderson@centtech.com) Received: from 10.20.200.100 (SquirrelMail authenticated user anderson); by otter.centtech.com with HTTP; Tue, 6 Jun 2006 07:50:42 -0500 (CDT) Message-ID: <62208.10.20.200.100.1149598242.squirrel@10.20.200.100> In-Reply-To: <44852CF1.5070300@introweb.nl> References: <44852CF1.5070300@introweb.nl> Date: Tue, 6 Jun 2006 07:50:42 -0500 (CDT) From: "Eric Anderson" To: "Robin Elfrink" User-Agent: SquirrelMail/1.5.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: ClamAV 0.87.1/1514/Mon Jun 5 15:21:02 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-isp@freebsd.org Subject: Re: Recovery from disk+fs crash X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2006 12:50:45 -0000 Robin Elfrink said: > > Hi, > > > I have a system with hardware raid, which has had some hardware troubles. > > The state this machine is in is now: The raid configuration is OK, but > the filesystem somehow broke seriously. If I mount it under FreeBSD 5.4 > (which is wat the system was running at the time) it completely _hangs_ > (not even kernel panic) when accessing certain directories. Under 6.x > not everything is OK, but at least the system does not hang. > > Now the problem is that I lost some directory trees, and I am looking > for ways to see if I recover them. The obvious first step would be fsck, > but the fs is so broken it gives me: > > root@:~# fsck /dev/da0s1f > ** /dev/da0s1f (NO WRITE) > cannot alloc 18446744067446403432 bytes for inphead > > root@:~# df -h /dev/da0s1f > Filesystem Size Used Avail Capacity Mounted on > /dev/da0s1f 64G -58T 58T -100219% /var/disk > > Google did not help much, has anybody any clue to how I can get fsck to > run properly? Have you tried using fsck_ffs and specifying an alternate superblock? (say 160) Eric -- ------------------------------------------------------------- Eric Anderson anderson@centtech.com Centaur Technology You have my continuous partial attention -------------------------------------------------------------