From owner-freebsd-questions@FreeBSD.ORG Tue Oct 14 00:02:41 2003 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 A864016A4B3 for ; Tue, 14 Oct 2003 00:02:41 -0700 (PDT) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6ACB43F75 for ; Tue, 14 Oct 2003 00:02:37 -0700 (PDT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id E13C42BD37 for ; Tue, 14 Oct 2003 17:02:33 +1000 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 90DC851835; Tue, 14 Oct 2003 16:32:21 +0930 (CST) Date: Tue, 14 Oct 2003 16:32:21 +0930 From: Greg 'groggy' Lehey To: Octavian Hornoiu Message-ID: <20031014070221.GY57013@wantadilla.lemis.com> References: <1066113972.1915.36.camel@phobos.lexis.int> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qn4G1eBrv+t66M9q" Content-Disposition: inline In-Reply-To: <1066113972.1915.36.camel@phobos.lexis.int> User-Agent: Mutt/1.4i 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: freebsd-questions@freebsd.org Subject: Re: big vinum problem 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, 14 Oct 2003 07:02:41 -0000 --Qn4G1eBrv+t66M9q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 13 October 2003 at 23:46:12 -0700, Octavian Hornoiu wrote: > After a power loss last night i restarted my server with a 425 gig or so > RAID-5 array and expected to go through a length fsck after which the > system would come up. However, one of the vinum subdisks was down. So, > i rebooted into single user mode, i restarted the home.p0.s3 subdisk and > then i ran a manual fsck. What followed was a series of hard errors > that said: > > ad7s1e: hard error reading fsbn 86482817 of 43241337-43241448 (ad7s1 bn > 86482817; cn 5383 tn 78 sn 8) status=59 error=40 > vinum: home.p0.s3 is crashed by force > vinum: home.p0 is degraded > fatal: home.p0.s3 read error, block 43241337 for 57344 bytes > home.p0.s3 user buffer block 30268632 for 57344 bytes > ** Phase 2 - Check Pathnames > ad11s1e hard error etc > > then home.p0.s7 becomes corrupt and crashes by force and then i find > myself staring at a screen that says: > > CANNOT READ: BLK 297103054 > CONTINUE [yn] > > > I have done this twice now and every time vinum successfully initializes > the subdisk and the plex comes up and is in the "up" state but once i > run fsck it crashes again. What exactly can i do to remedy this. If > it's a bad disk i'll replace it but can't vinum work around bad blocks? That depends on your configuration, which you haven't described. Take a look at http://www.vinumvm.org/vinum/how-to-debug.html. > My system is FreeBSD 4.9 RC from RELEASE branch with all the latest > patches, i'm fully up to date. I have 8 subdisks in vinum > home.p0.s0-s7 with a 55 GB partition on each drive used by vinum. > All the drives are identical and all they contain is the vinum > partitions. It looks as if you have only one plex, then. Vinum doesn't normally recover from these problems. It follows a slightly different policy from UFS: if there are bad sectors on a subdisk, it doesn't trust the entire subdisk. There are ways around this, but they haven't been committed. Send me the information asked for on the web page and I'll send you instructions on how to fix the problem. This still means that you'll probably have to change the disk. 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. --Qn4G1eBrv+t66M9q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/i599IubykFB6QiMRAgAtAKCCeV5Uw50bgRrdIdMxEyrDdEzORwCfWqok b2cORIVBwfUUdp8o32aSMKg= =k5Eb -----END PGP SIGNATURE----- --Qn4G1eBrv+t66M9q--