From owner-freebsd-questions@FreeBSD.ORG Wed Aug 25 10:08:58 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 957A616A4CE for ; Wed, 25 Aug 2004 10:08:58 +0000 (GMT) Received: from pfepb.post.tele.dk (pfepb.post.tele.dk [195.41.46.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2235743D2D for ; Wed, 25 Aug 2004 10:08:58 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from ferengi.borderworlds.dk (ferengi.borderworlds.dk [80.166.152.7]) by pfepb.post.tele.dk (Postfix) with ESMTP id 34D835EE047 for ; Wed, 25 Aug 2004 12:08:55 +0200 (CEST) Received: from borg.borderworlds.dk (localhost [127.0.0.1]) by ferengi.borderworlds.dk (Postfix) with ESMTP id 464CEB825 for ; Wed, 25 Aug 2004 12:08:54 +0200 (CEST) Received: by borg.borderworlds.dk (Postfix, from userid 1001) id DDDC7B86E; Wed, 25 Aug 2004 12:08:53 +0200 (CEST) Sender: xi@borderworlds.dk To: freebsd-questions@freebsd.org References: <20040825083123.GD17106@pcwin002.win.tue.nl> From: Christian Laursen Date: 25 Aug 2004 12:08:53 +0200 In-Reply-To: <20040825083123.GD17106@pcwin002.win.tue.nl> Message-ID: <86pt5f1qdm.fsf@borg.borderworlds.dk> Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: vinum rebuildparity, when? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Aug 2004 10:08:58 -0000 Stijn Hoop writes: > I was wondering about the vinum 'rebuildparity' command, especially the > times when one needs to use this. I run rebuildparity if checkparity finds any errors after unclean shutdowns. > The problem is that I can't find anything in the vinum docs about this > command other than it's purpose. What I don't understand is the difference > between reviving a disk in a RAID-5 plex, and rebuilding the parity. When reviving a disk the data on that disk is calculated from the data and the parity on the other disks. I think rebuildparity only reads data and writes the parity calculated from that but for all disks. > When I start a degraded disk it starts to revive -- which led me to believe > that vinum was also recalculating the parity. Evidently it wasn't. > I'm therefore now updating my procedures to always run 'checkparity -v ' > after a disk crash. That shouldn't be neccesary. > Does anyone know if this is supposed to be this way? I'm pretty sure, that it isn't. -- Christian Laursen