From owner-freebsd-current@FreeBSD.ORG Thu Apr 8 14:45:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E518B16A4CE for ; Thu, 8 Apr 2004 14:45:47 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBBF543D5D for ; Thu, 8 Apr 2004 14:45:47 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id C27FC72DCA; Thu, 8 Apr 2004 14:45:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id BDA2172DBF; Thu, 8 Apr 2004 14:45:47 -0700 (PDT) Date: Thu, 8 Apr 2004 14:45:47 -0700 (PDT) From: Doug White To: Will Saxon In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED802E86938@bragi.housing.ufl.edu> Message-ID: <20040408144512.P13329@carver.gumbysoft.com> References: <0E972CEE334BFE4291CD07E056C76ED802E86938@bragi.housing.ufl.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: RE: drive failure, now 'cannot alloc 494581644 bytes for inoinfo' and 'bad inode number 3556352 to nextinode' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2004 21:45:48 -0000 On Tue, 6 Apr 2004, Will Saxon wrote: > > I can pretty much assure you the volume isn't OK. The types of errors > > you're seeing are indicative of severe corruption, usually > > due to random > > data being written over critical filesystem blocks. I'd > > suggest running a > > parity verify against the volume to force corrections to start with -- > > this can't make it any worse than it already is, and may recover the > > damaged blocks on the disk that lost power. > > > > Is there a freebsd tool that will let me do the parity verify? This > controller has the most minimal BIOS interface possible, I think they > want all the real work to be done through a windows utility. No, since its a function of your RAID controller. FreeBSD just sees one opaque volume. You may wish to consider a more robust RAID controller :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org