From owner-freebsd-isp@FreeBSD.ORG Tue Jun 6 14:50:46 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 7852A16BD81 for ; Tue, 6 Jun 2006 14:50:46 +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 EAF8B43D45 for ; Tue, 6 Jun 2006 14:50:45 +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 ECBB0C382A; Tue, 6 Jun 2006 16:50:43 +0200 (CEST) Received: from [192.168.0.26] (mail.introweb.net [80.65.97.195]) by frontend1.mailcluster.introweb.intern (Postfix) with ESMTP id CB41C1BAC11; Tue, 6 Jun 2006 16:52:39 +0200 (CEST) Message-ID: <44859643.6030005@introweb.nl> Date: Tue, 06 Jun 2006 16:50:43 +0200 From: Robin Elfrink User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <44852CF1.5070300@introweb.nl> <62208.10.20.200.100.1149598242.squirrel@10.20.200.100> <44857BA4.90405@introweb.nl> <56782.10.20.200.100.1149599550.squirrel@10.20.200.100> In-Reply-To: <56782.10.20.200.100.1149599550.squirrel@10.20.200.100> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 14:50:55 -0000 Eric Anderson wrote: > You could go in with fsdb and fix the parts manually, but it wouldn't be > simple. You might also try a 'preen' first - not sure if that will do > anything different. Also - this fs is not currently mounted at all, > right? I have no experience with fsdb, so that will take some time for me to read the manuals. The filesystem was mounted read-only just then, but fsck_uff -b 160 /dev/da0s1f only says it copies the block, and leaves the filesystem dirty. root@:~# fsck_ffs -b 160 /dev/da0s1f Alternate super block location: 160 ** /dev/da0s1f cannot alloc 188446744067446403432 bytes for inphead UPDATE STANDART SUPERBLOCK? [yn] y ***** FILE SYSTEM STILL DIRTY ***** I tried with several backup copies (as newfs -N said it would make; this is a standard install with no fs optimizations). All with the same result. Robin