From owner-freebsd-stable@FreeBSD.ORG Fri Oct 31 10:34:10 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A12916A4CE for ; Fri, 31 Oct 2003 10:34:10 -0800 (PST) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AB9843F75 for ; Fri, 31 Oct 2003 10:34:09 -0800 (PST) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.9p2/8.12.9) with ESMTP id h9VIFeLq085571; Fri, 31 Oct 2003 21:15:40 +0300 (MSK) (envelope-from marck@rinet.ru) From: Dmitry Morozovsky To: Mike Maltese In-Reply-To: <001d01c39fcc$51accdd0$f4f0a8c0@pcmedx.com> Message-ID: <20031031211035.W81511@woozle.rinet.ru> References: <20031031153427.P81511@woozle.rinet.ru> <001d01c39fcc$51accdd0$f4f0a8c0@pcmedx.com> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@FreeBSD.org Subject: Re: vinum question: how could one correctly delete vinum module? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Fri, 31 Oct 2003 18:34:10 -0000 X-Original-Date: Fri, 31 Oct 2003 21:15:40 +0300 (MSK) X-List-Received-Date: Fri, 31 Oct 2003 18:34:10 -0000 On Fri, 31 Oct 2003, Mike Maltese wrote: MM> > [I'm under 4-STABLE] MM> > MM> > What is the correct sequence to delete existing vinum module (for example, MM> > raid10) and do *not* use -f flags for vinum? MM> > MM> > in my case t is raid10 vovume: MM> > MM> > vinum -> l -r t MM> > V t State: up Plexes: 2 Size: 8191 MM> > P t.p0 S State: up Subdisks: 2 Size: 8191 MM> > P t.p1 S State: up Subdisks: 2 Size: 8191 MM> > S t.d0 State: up PO: 0 B Size: 4095 MM> > S t.d8 State: up PO: 260 kB Size: 4095 MM> > S t.d2 State: up PO: 0 B Size: 4095 MM> > S t.d10 State: up PO: 260 kB Size: 4095 MM> > MM> > umount /dev/vinum/t MM> > vinum stop t (ok) MM> > vinum stop t.p0 <- this operation silently puts t up, and sets t.p0 faulty MM> > vinum stop t (ok) MM> > vinum stop t.p1 MM> > MM> > Last comment leads to error MM> > MM> > Can't stop t.p1: Device busy (16) MM> > MM> > MM> > Final state of objects are MM> > MM> > vinum -> l -r t MM> > V t State: down Plexes: 2 Size: 8191 MM> > P t.p0 S State: faulty Subdisks: 2 Size: 8191 MM> > P t.p1 S State: up Subdisks: 2 Size: 8191 MM> > S t.d0 State: down PO: 0 B Size: 4095 MM> > S t.d8 State: down PO: 260 kB Size: 4095 MM> > S t.d2 State: up PO: 0 B Size: 4095 MM> > S t.d10 State: up PO: 260 kB Size: 4095 MM> > MM> > Any suggestions? should I dig into vinum sources to track this down? MM> MM> You want to wipe out your configuration completely? Use "vinum resetconfig". MM> You will loose all of your data, but if I understand your question MM> correctly, this is the command to use. If you want to remove individual MM> objects, use the rm command. Take a look at the vinum man page, it is quite MM> useful. Well, not exactly ;-) And, yes, I'm aware of "resetconfig" command. Possibly, I was not clear enough; I should also mention 'detach' command. Detaching without -f option also does not work usually. As for 'rm' command, it tends to fail in similar way ;-) Which is worse, it at lease seems that some objects got slided and slightly resized after multiple detach/attaches; but I should track this down more precisely, and currently in lack of spare system. Stay tuned ;-) Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------