From owner-freebsd-questions@FreeBSD.ORG Wed Feb 11 19:30:53 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 4385316A4CF for ; Wed, 11 Feb 2004 19:30:53 -0800 (PST) Received: from freep.dyns.net (adsl-63-195-184-183.dsl.snfc21.pacbell.net [63.195.184.183]) by mx1.FreeBSD.org (Postfix) with SMTP id EA3A043D31 for ; Wed, 11 Feb 2004 19:30:52 -0800 (PST) (envelope-from micheas@micheas.dyns.net) Received: (qmail 12210 invoked from network); 12 Feb 2004 03:30:52 -0000 Received: from tux.a (HELO tux) (mail@10.0.0.173) by sol.a with SMTP; 12 Feb 2004 03:30:52 -0000 Received: from micheas by tux with local (Exim 3.36 #1 (Debian)) id 1Ar7Yy-0000gV-00; Wed, 11 Feb 2004 19:30:52 -0800 From: Micheas Herman To: Greg 'groggy' Lehey In-Reply-To: <20040212010235.GV8342@wantadilla.lemis.com> References: <20040204185203.GA14302@pcwin002.win.tue.nl> <20040212010235.GV8342@wantadilla.lemis.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Free Print Shop Message-Id: <1076556652.846.24.camel@tux> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 11 Feb 2004 19:30:52 -0800 Sender: Micheas Herman cc: dontspamhenk@xs4all.nl cc: freebsd-questions@freebsd.org Subject: Re: Fixing vinum after removing a HDD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: micheas@freep.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2004 03:30:53 -0000 On Wed, 2004-02-11 at 17:02, Greg 'groggy' Lehey wrote: > On Wednesday, 4 February 2004 at 19:52:03 +0100, Stijn Hoop wrote: > > On Wed, Feb 04, 2004 at 07:41:48PM +0100, dontspamhenk@xs4all.nl wrote: > >> I'm running FreeBSD 4.8 on a system with 5 HDD's. ad0 is to be removed > >> from the system. ad1, ad2 and ad3 contain my vinum drives. FreeBSD resides > >> on the last disk (da0). > >> > >> Can anyone tell me if the following procedure is the right way to do it? > >> 1. physically remove ad0 > >> 2. vinum resetconfig > >> 3. change drivenumbers in vinum.conf > >> 4. run vinum with the new configfile > > > > As far as my (limited) vinum knowledge goes, you really don't need to do a > > resetconfig. > > Correct. From the man page: > > resetconfig > The resetconfig command completely obliterates the vinum configu- > ration on a system. Use this command only when you want to com- > pletely delete the configuration. > > I'm completely baffled that people want to use this command so much. > The correct sequence is to remove the drive, replace it with something > else with a Vinum partition, and then start the defective objects. Just a guess (arm chair psychology of users), but I suspect it is because they are thinking that they need to "re-setup" their drive. Maybe deleteconfig would be a more self documenting flag. Micheas > > It depends on the volume structures as to whether the data can still > be recovered. > > 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. -- Micheas Herman email: micheas@freep.org Free Print Shop web: http://www.FreePrintShop.org phone: (415)648-3222 fax: (415)648-4466