From owner-freebsd-questions@FreeBSD.ORG Tue Mar 16 03:13:30 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DB5416A4CE for ; Tue, 16 Mar 2004 03:13:30 -0800 (PST) Received: from support.antlabs.com (unknown [203.117.181.12]) by mx1.FreeBSD.org (Postfix) with SMTP id B481E43D2F for ; Tue, 16 Mar 2004 03:13:28 -0800 (PST) (envelope-from grog@adelaide.lemis.com) Received: (qmail 12443 invoked from network); 16 Mar 2004 11:20:26 -0000 Received: from unknown (HELO adelaide.lemis.com) (192.168.22.230) by 0 with SMTP; 16 Mar 2004 11:20:26 -0000 Received: by adelaide.lemis.com (Postfix, from userid 1004) id DAC9517FC4; Tue, 16 Mar 2004 19:13:25 +0800 (CST) Date: Tue, 16 Mar 2004 19:13:25 +0800 From: Greg Lehey To: Lewis Thompson Message-ID: <20040316111325.GB742@adelaide.lemis.com> References: <20040316020000.GA846@lewiz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040316020000.GA846@lewiz.org> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: questions@freebsd.org Subject: Re: Vinum, replaced disk -- fsck error. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2004 11:13:30 -0000 On Tuesday, 16 March 2004 at 2:00:00 +0000, Lewis Thompson wrote: > Hi, > > I had a failed disk in my RAID-0 Vinum array. This was a physical disk > problem and in an attempt to recover as much data as possible I dd'ed it > to another disk (dd if=ad3 of=ad1 bs=8192 conv=noerror). This may or may not work, depending on details you haven't reported. > This has mostly gone fine (bar the I/O errors that were to be > expected) and I can actually start vinum and mount the RAID-0 array > with no trouble (Vinum reports no errors I can see). I suppose that depends on where you look :-) Read on. > I don't really know how I can test the integrity of files from the > replaced disk... A good start would be to read the documentation at http://www.vinumvm.org/. > I attempted to fsck the volume before I mounted it but I first had to > restore the superblock for the volume (tunefs -A /dev/vinum/data), which > worked fine. However (and this is my real problem), fsck_ufs > /dev/vinum/data gives the following message: > > ** /dev/vinum/data > cannot alloc 4316869296 bytes for inphead > > ***** FILE SYSTEM STILL DIRTY ***** Possibly there are log messages that go with this message. It indicates to me that there's something seriously wrong in some data structure, and that fsck is asking for a ridiculous amount of memory as a result. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers