Date: Wed, 19 Mar 2003 11:43:31 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Tillman <tillman@seekingfire.com> Cc: FreeBSD-Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Migrating vinum plexes to a new volume Message-ID: <20030319011331.GB44448@wantadilla.lemis.com> In-Reply-To: <20030318140749.V5477@seekingfire.com> References: <20030317150055.C5477@seekingfire.com> <20030317233424.GE9422@wantadilla.lemis.com> <20030318140749.V5477@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--dTy3Mrz/UPE2dbVg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 18 March 2003 at 14:07:49 -0600, Tillman wrote: > 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) This means that it has plexes attached. > vinum -> stop iso2.p0 > vinum -> stop iso2.p1 > Can't stop iso2.p1: Device busy (16) This means that stopping the plex would take the volume down. You need -f here. > 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) Same here. > 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 ;-) Well, it will cause lack of availability to take it down. I think that's reasonable. The point is that taking iso2.p0 down doesn't make the data unavailable, so there should be a difference between the two. > 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. Correct. > 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. I suppose it's a judgment call. Anyway, the way to get rid of iso2 is: vinum -> rm -rf iso2 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 --dTy3Mrz/UPE2dbVg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+d8Q7IubykFB6QiMRAmlDAJ0TW4weN0zgbB9o6rL0VyzpKW3R8QCff216 tMHmi5iIj/oRz8RVuLIuF9g= =13ZZ -----END PGP SIGNATURE----- --dTy3Mrz/UPE2dbVg-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030319011331.GB44448>