From owner-freebsd-questions Tue Mar 18 12: 3:51 2003 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 9371937B401 for ; Tue, 18 Mar 2003 12:03:49 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8534F43FB1 for ; Tue, 18 Mar 2003 12:03:48 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: from blues.seekingfire.prv (blues.seekingfire.prv [192.168.23.211]) by mail.seekingfire.com (Postfix) with ESMTP id 74BAB1A9 for ; Tue, 18 Mar 2003 14:03:47 -0600 (CST) Received: (from tillman@localhost) by blues.seekingfire.prv (8.11.6/8.11.6) id h2IK7n310126 for freebsd-questions@FreeBSD.ORG; Tue, 18 Mar 2003 14:07:49 -0600 Date: Tue, 18 Mar 2003 14:07:49 -0600 From: Tillman To: FreeBSD-Questions Subject: Re: Migrating vinum plexes to a new volume Message-ID: <20030318140749.V5477@seekingfire.com> References: <20030317150055.C5477@seekingfire.com> <20030317233424.GE9422@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030317233424.GE9422@wantadilla.lemis.com>; from grog@FreeBSD.ORG on Tue, Mar 18, 2003 at 10:04:24AM +1030 X-Urban-Legend: There is lots of hidden information in headers Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Mar 18, 2003 at 10:04:24AM +1030, Greg 'groggy' Lehey wrote: > On Monday, 17 March 2003 at 15:00:55 -0600, Tillman wrote: > > What you want to do is to remove the plexes iso2.p[01], and attach > their subdisks to iso.p[01]. That will increase the size of those > plexes to 5.5GB. Then run growfs. I seem to have run into a "device busy" problem. Here's what I've done: [root@athena root]# mount | grep iso2 (no output - volume iso2 is not mounted) [root@athena root]# vinum vinum -> stop iso2 vinum -> lv iso2 V iso2 State: down Plexes: 2 Size: 1500MB vinum -> rm iso2 Can't remove iso2: Device busy (16) vinum -> stop iso2.p0 vinum -> stop iso2.p1 Can't stop iso2.p1: Device busy (16) vinum -> ls iso2.p0.s0 S iso2.p0.s0 State: down PO: 0 B Size: 1500 MB vinum -> ls iso2.p1.s0 S iso2.p1.s0 State: up PO: 0 B Size: 1500 MB vinum -> stop iso2.p1.s0 Can't stop iso2.p1.s0: Device busy (16) I don't appear to be able to stop the other half of the mirror in order to be able to successfully rm the volume and the plexes. I haven't tried the -f option due to dire warnings in the man page ;-) My current train of thought is that the mirror is still "active" in some sense, and thus vinum is protecting the mirroring when I want to stop both halves of it. The manual says "By default, vinum does not stop active objects." However, I don't know what would be making it active - it's not mounted and I seem to be unable to stop all of the volumes subordinate objects. > > Are there any potential pitfalls involving dataloss? > > You'll lose all data on iso2. That's fine, it was volume iso I was worried about. Thanks for sharing your time, -T -- "...you could spend *all day* customizing the title bar. Believe me. I speak from experience." - Matt Welsh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message