From owner-freebsd-questions@FreeBSD.ORG Wed Feb 4 10:51:44 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 B8F1A16A4CE for ; Wed, 4 Feb 2004 10:51:44 -0800 (PST) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FFC843D55 for ; Wed, 4 Feb 2004 10:51:40 -0800 (PST) (envelope-from stijn@pcwin002.win.tue.nl) Received: from pcwin002.win.tue.nl (orb_rules@localhost [127.0.0.1]) by pcwin002.win.tue.nl (8.12.10/8.12.10) with ESMTP id i14Iq3UA014514; Wed, 4 Feb 2004 19:52:03 +0100 (CET) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.12.10/8.12.10/Submit) id i14Iq3gA014513; Wed, 4 Feb 2004 19:52:03 +0100 (CET) (envelope-from stijn) Date: Wed, 4 Feb 2004 19:52:03 +0100 From: Stijn Hoop To: dontspamhenk@xs4all.nl Message-ID: <20040204185203.GA14302@pcwin002.win.tue.nl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Bright-Idea: Let's abolish HTML mail! 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 List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 18:51:44 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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). >=20 > 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. Vinum writes the configuration to the disk and reads the information from i= t. I think it will be able to cope with a missing disk by itself because the label on it has not changed; on what is now /dev/ad1s1h vinum has stored the fact that this vinum drive is labeled 'a', and even if the freebsd device node changes names, vinum will still know that the then /dev/ad0s1h is labeled 'a'. Unfortunately this is only my understanding and I haven't yet needed to do such an operation for real. YMMV. --Stijn --=20 The right half of the brain controls the left half of the body. This means that only left handed people are in their right mind. --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAIT9TY3r/tLQmfWcRAvzVAJ9TMpto2r36c5yVLiI8llLwYLRccQCeIAA/ GKA6y8WstVadvT+XVBUYkn8= =uRR+ -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--