From owner-freebsd-questions@FreeBSD.ORG Wed Apr 14 16:20:56 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 B0E0F16A4CF for ; Wed, 14 Apr 2004 16:20:56 -0700 (PDT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B682143D45 for ; Wed, 14 Apr 2004 16:20:55 -0700 (PDT) (envelope-from peter.schuller@infidyne.com) Received: from scode.mine.nu ([213.113.221.56] [213.113.221.56]) by mxfep01.bredband.com with ESMTP id <20040414232054.TVVO7099.mxfep01.bredband.com@scode.mine.nu> for ; Thu, 15 Apr 2004 01:20:54 +0200 Received: from localhost (localhost [127.0.0.1]) by scode.mine.nu (Postfix) with ESMTP id 84808114D6E for ; Thu, 15 Apr 2004 01:21:04 +0200 (CEST) From: Peter Schuller To: freebsd-questions@freebsd.org Date: Thu, 15 Apr 2004 01:21:02 +0200 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200404150121.02270.peter.schuller@infidyne.com> Subject: Vinum: How to safely remove a volume/drive from the configuration 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, 14 Apr 2004 23:20:56 -0000 Hello, so I had set up a rudimentary vinum configuration. I eventually rebooted the machine to make sure everything came up again correctly. It did, but it also picked up a couple of old drives and volumes that I had previously used for testing. "vinum l" now yields: 3 drives: D alpha State: up /dev/da0a A: 17244/488 MB (3532%) D backup_a_1 State: up /dev/ad1s1b A: 31/19531 MB (0%) D backup_a_2 State: up /dev/ad0s1a A: 39/19539 MB (0%) D beta State: referenced unknown A: 0/0 MB 3 volumes: V test State: up Plexes: 2 Size: 10 MB V test3 State: up Plexes: 1 Size: 20 MB V backup_a State: up Plexes: 2 Size: 19 GB 5 plexes: P test.p0 C State: up Subdisks: 1 Size: 10 MB P test.p1 C State: faulty Subdisks: 1 Size: 10 MB P test3.p0 C State: up Subdisks: 1 Size: 20 MB P backup_a.p0 C State: up Subdisks: 1 Size: 19 GB P backup_a.p1 C State: up Subdisks: 1 Size: 19 GB 5 subdisks: S test2.p0.s0 State: up D: alpha Size: 10 MB S test2.p1.s0 State: crashed D: beta Size: 10 MB S test3.p0.s0 State: up D: alpha Size: 20 MB S backup_a.p0.s0 State: up D: backup_a_1 Size: 19 GB S backup_a.p1.s0 State: up D: backup_a_2 Size: 19 GB The drives 'alpha' and 'beta', along with volumes 'test' and 'test3' are old remnants. The question now is - how do I correctly and safely purge them from my vinum configuration? I tried: scode-whitestar# vinum stop test scode-whitestar# vinum stop test3 scode-whitestar# vinum rm -r test Can't remove test: Device busy (16) As I interpret the manpage, the use of '-f' should not be required. And indeed, I assume that '-f' should never be needed unless in extreme cases? In any case. At the moment my vinum configuration *is* expendable since I have not stored any data on any of the volumes yet, however I want to know how to do this correctly so that I can do it on a live system in the future. Btw, after 'vinum stop', the volumes state show as 'down'. But after an attempted rm -r, they go back to state 'up' (both test and test3, even though I only try to remove test). -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org