From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 16:18:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A17516A4CE; Mon, 8 Nov 2004 16:18:48 +0000 (GMT) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2724243D1D; Mon, 8 Nov 2004 16:18:48 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-151-199-90-129.roa.east.verizon.net [151.199.90.129]) by gromit.dlib.vt.edu (8.13.1/8.13.1) with ESMTP id iA8GIUtA060102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Nov 2004 11:18:31 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1) with ESMTP id iA8GIOBu071516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Nov 2004 11:18:25 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1/Submit) id iA8GINiM071515; Mon, 8 Nov 2004 11:18:23 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) X-Authentication-Warning: zappa.Chelsea-Ct.Org: paul set sender to paul@gromit.dlib.vt.edu using -f From: Paul Mather To: freebsd-current@freebsd.org In-Reply-To: <20041108083735.F1D2B16A4CF@hub.freebsd.org> References: <20041108083735.F1D2B16A4CF@hub.freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1099930701.71383.17.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 08 Nov 2004 11:18:22 -0500 cc: Andy Farkas Subject: Re: gvinum remains broken in 5.3-RELEASE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 16:18:48 -0000 On Mon, 8 Nov 2004 08:41:00 +0100 (CET), Lukas Ertl wrote: > On Mon, 8 Nov 2004, Andy Farkas wrote: > > > gvinum found lots more old info than I initially saw. > > > > Apparently I now have 1 extra physical drive, 2 extra > > volumes, and 8 extra subdisks. How do Iget rid of > > these old objects? > > gvinum rm -r Recently, when I tried to used "gvinum rm -r" to remove a plex belonging to a mirrored volume, gvinum complained about the subdisk and wouldn't remove the plex. I was able to remove the plex successfully by doing a "gvinum rm " followed by "gvinum rm ". Somewhat worryingly, after the "gvinum rm ", its plex was still marked "up" and not "down." The system was in a quiescent state, so nothing bad happened, but I couldn't help wondering what would have occurred had the system been active and the mirrored volume been written to (and hence writes attempted on the plex sans subdisk) between the two commands. BTW, I'd tried to "gvinum stop " the plex in question before removing it (a la classic vinum), but discovered that despite the gvinum internal help stating that functionality was supported, it isn't. Looking at gvinum.c confirmed this: gvinum's "stop" will only stop gvinum itself (and attempt to unload the geom_vinum module), not specific objects. FWIW, this is on a very recent 6.0-CURRENT. Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa