From owner-freebsd-questions@FreeBSD.ORG Thu Dec 9 02:07:04 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 B021616A4CE for ; Thu, 9 Dec 2004 02:07:04 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8DE743D31 for ; Thu, 9 Dec 2004 02:07:02 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id AF06685657; Thu, 9 Dec 2004 12:36:56 +1030 (CST) Date: Thu, 9 Dec 2004 12:36:56 +1030 From: Greg 'groggy' Lehey To: Stijn Hoop , Scott Mitchell , orville weyrich , freebsd-questions@freebsd.org Message-ID: <20041209020656.GG92212@wantadilla.lemis.com> References: <20041208054552.71553.qmail@web50708.mail.yahoo.com> <20041208100905.GA12684@tuatara.fishballoon.org> <20041208105255.GW39558@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4RKFTa9IRjtxz5WY" Content-Disposition: inline In-Reply-To: <20041208105255.GW39558@pcwin002.win.tue.nl> User-Agent: Mutt/1.4.2.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 Subject: Re: Has anybody EVER successfully recovered VINUM? 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: Thu, 09 Dec 2004 02:07:04 -0000 --4RKFTa9IRjtxz5WY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 8 December 2004 at 11:52:55 +0100, Stijn Hoop wrote: > Scott, your procedure is what I have used, except for: > > On Wed, Dec 08, 2004 at 10:09:05AM +0000, Scott Mitchell wrote: >> 6. Tell vinum to restart the failed subdisk: >> >> # vinum start raid.p0.s0 >> >> 7. Wait ages while the new disk is 'revived'. >> >> I was quite impressed that the volume remained available with users >> accessing it throughout this procedure :-) > > Yes I was too -- however I wasn't as impressed with the fact that I had parity > errors afterwards. Have you run 'vinum checkparity' after these rebuilds? In > my case I suffered data corruption... *sigh* Yes, there's some problem there. > AFAIK the only way to guarantee a consistent rebuild is to do it > offline (at least in 4.x, haven't tested gvinum in 5.x yet). > >> To play it safe you might want to unmount the volume before starting. > > I *have* to. The issue is contention round where stripes are being written. The code *should* avoid the contention, but it appears that there's a bug there somewhere. I certainly agree with you that you should umount the file system first. There's no reason to believe that this problem exists in gvinum: I believe the code has been completely rewritten. Greg -- See complete headers for address and phone numbers. --4RKFTa9IRjtxz5WY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBt7NAIubykFB6QiMRAmkGAKCn6LzcrM8HM5XIqvy8zBk9BKXrJgCdFI3o R2Pkt30zIg2YGsrC4cn+QSk= =CYot -----END PGP SIGNATURE----- --4RKFTa9IRjtxz5WY--