From owner-freebsd-isp@FreeBSD.ORG Tue Jun 6 07:23:10 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 2BD3E16A903 for ; Tue, 6 Jun 2006 07:20:55 +0000 (UTC) (envelope-from elfrink@introweb.nl) Received: from relay.introweb.nl (relay.introweb.nl [80.65.96.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1D6643D48 for ; Tue, 6 Jun 2006 07:20:54 +0000 (GMT) (envelope-from elfrink@introweb.nl) Received: from smtp.introweb.nl (frontend1.mailcluster.introweb.intern [192.168.4.31]) by relay3.introweb.nl (Postfix) with ESMTP id F24ADC392A for ; Tue, 6 Jun 2006 09:20:52 +0200 (CEST) Received: from [192.168.0.26] (mail.introweb.net [80.65.97.195]) by frontend1.mailcluster.introweb.intern (Postfix) with ESMTP id E6CBA1BAC16 for ; Tue, 6 Jun 2006 09:22:48 +0200 (CEST) Message-ID: <44852CF1.5070300@introweb.nl> Date: Tue, 06 Jun 2006 09:21:21 +0200 From: Robin Elfrink User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-isp@freebsd.org X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: 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 07:23:17 -0000 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? Robin