Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Nov 2003 10:25:46 +0800
From:      Greg Lehey <grog@lemis.com>
To:        Dmitry Morozovsky <marck@rinet.ru>, Mike Maltese <mike@pcmedx.com>
Cc:        stable@FreeBSD.org
Subject:   Re: vinum question: how could one correctly delete vinum module?
Message-ID:  <20031102022546.GA3275@adelaide.lemis.com>
In-Reply-To: <001d01c39fcc$51accdd0$f4f0a8c0@pcmedx.com> <20031031153427.P81511@woozle.rinet.ru>
References:  <20031031153427.P81511@woozle.rinet.ru> <001d01c39fcc$51accdd0$f4f0a8c0@pcmedx.com> <20031031153427.P81511@woozle.rinet.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 31 October 2003 at 15:41:42 +0300, Dmitry Morozovsky wrote:
> Dear colleagues,
>
> [I'm under 4-STABLE]
>
> What is the correct sequence to delete existing vinum module (for example,
> raid10) and do *not* use -f flags for vinum?

I think your terminology is incorrect.  To delete an existing Vinum
module under release 4, you would normally do:

  # rm /modules/vinum.ko 

To unload the module from the kernel, you would first quiesce the
Vinum system and then do:

  # vinum stop

But I'd guess that this isn't what you want to do.

> in my case t is raid10 vovume:
>
> vinum -> l -r t
> V t                     State: up       Plexes:       2 Size:       8191 MB
> P t.p0                S State: up       Subdisks:     2 Size:       8191 MB
> P t.p1                S State: up       Subdisks:     2 Size:       8191 MB
> S t.d0                  State: up       PO:        0  B Size:       4095 MB
> S t.d8                  State: up       PO:      260 kB Size:       4095 MB
> S t.d2                  State: up       PO:        0  B Size:       4095 MB
> S t.d10                 State: up       PO:      260 kB Size:       4095 MB

These subdisk names are very confusing.

> umount /dev/vinum/t
> vinum stop t (ok)
> vinum stop t.p0 <- this operation silently puts t up, and sets t.p0 faulty
> vinum stop t (ok)
> vinum stop t.p1
>
> Last comment leads to error
>
> Can't stop t.p1: Device busy (16)

Why do you want to stop a plex?

> Final state of objects are
>
> vinum -> l -r t
> V t                     State: down     Plexes:       2 Size:       8191 MB
> P t.p0                S State: faulty   Subdisks:     2 Size:       8191 MB
> P t.p1                S State: up       Subdisks:     2 Size:       8191 MB
> S t.d0                  State: down     PO:        0  B Size:       4095 MB
> S t.d8                  State: down     PO:      260 kB Size:       4095 MB
> S t.d2                  State: up       PO:        0  B Size:       4095 MB
> S t.d10                 State: up       PO:      260 kB Size:       4095 MB
>
> Any suggestions? should I dig into vinum sources to track this down?

Well, I think you know the answer: use the -f flag.  But maybe I'm
misunderstanding the question.

On Friday, 31 October 2003 at  8:30:38 -0800, Mike Maltese wrote:
>> Any suggestions? should I dig into vinum sources to track this down?
>
> You want to wipe out your configuration completely?

I don't think so.

> Use "vinum resetconfig".  You will loose all of your data, but if I
> understand your question correctly, this is the command to use. If
> you want to remove individual objects, use the rm command. Take a
> look at the vinum man page, it is quite useful.

As far as I can tell, he doesn't want to remove anything.

Greg
--
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031102022546.GA3275>