From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 20 09:29:02 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 054FD16A4CE for ; Tue, 20 Jul 2004 09:29:02 +0000 (GMT) Received: from mail022.syd.optusnet.com.au (mail022.syd.optusnet.com.au [211.29.132.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id E948D43D41 for ; Tue, 20 Jul 2004 09:29:00 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i6K9Snk10751; Tue, 20 Jul 2004 19:28:51 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i6K9SmVd006364; Tue, 20 Jul 2004 19:28:48 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i6K9SmMs006363; Tue, 20 Jul 2004 19:28:48 +1000 (EST) (envelope-from pjeremy) Date: Tue, 20 Jul 2004 19:28:48 +1000 From: Peter Jeremy To: Charles Sprickman Message-ID: <20040720092848.GD3001@cirb503493.alcatel.com.au> References: <20040719191408.V28049@toad.nat.fasttrackmonkey.com> <20040720021432.O28049@toad.nat.fasttrackmonkey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040720021432.O28049@toad.nat.fasttrackmonkey.com> User-Agent: Mutt/1.4.2i cc: freebsd-hackers@freebsd.org Subject: Re: disk recovery help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 09:29:02 -0000 On Tue, 2004-Jul-20 02:18:00 -0400, Charles Sprickman wrote: >And for the most part I can move around the filesystem, read files, etc. >But it is in a very inconsistent state. How can I make fsck work on this? >There's data there, but looking into certain dirs panics the box (it is It's difficult to see how a sanely written RAID utility could totally screw up an array in a short time - a 'build' utility presumably writes known data to the array but logically it would do so sequentially. The only thing I can think of is that the controller had a significant amount of cached data - which has been wiped, rather than written back to the disk. If you haven't run newfs and have the correct disklabel, the disk should be in a reasonably sane state. Have you tried running something like ports/sysutils/scan_ffs over the disk (or your copy of it)? Have you tried dumping vn0c? -- Peter Jeremy