On Monday, 11 October 1999 at 9:46:08 +0300, Narvi wrote:
>
> On Mon, 11 Oct 1999, Greg Lehey wrote:
>
>> On Sunday, 10 October 1999 at 19:33:44 +0300, Narvi wrote:
>>>
>>> Should you decide to use vinum keep in mind that you:
>>>
>>> a) reboot to make sure that whatever you just set up can
>>> automatically start itself
>>
>> This is always a good idea. You don't have to do it immediately, of
>> course.
>>
>>> b) alternatively
>>> vinum l
>>> vinum makedev
>>> vinum create -f configfile
>>> vinum start
>>> is your friend and avoids most of the problem
>>
>> I don't understand why you would want to do this. You certainly don't
>> want vinum create followed by vinum start.
>
> Well, maybe 'vinum start' is not needed.
In fact, *only* 'vinum start' is needed. From vinum(8):
start [-w] [volume | plex | subdisk]
start starts (brings into to the up state) one or more vinum ob-
jects.
If no object names are specified, vinum scans the disks known to
the system for vinum drives and then reads in the configuration
as described under the read commands. The vinum drive contains a
header with all information about the data stored on the drive,
including the names of the other drives which are required in or-
der to represent plexes and volumes.
> vinum l -> load vinum, but not teh disk conf
No. From vinum(8):
list [-r] [-V] [volume | plex | subdisk]
l [-r] [-V] [volume | plex | subdisk]
list is used to show information about the specified object. If
the argument is omitted, information is shown about all objects
known to vinum. The l command is a synonym for list.
> vinum makedev -> clean the /dev/vinum directory
In emergencies. From vinum(8):
makedev
The makedev command removes the directory /dev/vinum and recre-
ates it with device nodes which reflect the current configura-
tion. This command is not intended for general use, and is pro-
vided for emergency use only.
> vinum create ... -> tell vinum what the setup is.
Well, create new objects. From vinum(8):
create [-f description-file]
vinum create is used to create any object. ... Note
that the vinum create function is additive: if you run it
multiple times, you will create multiple copies of all
unnamed objects.
>>> IMHO it should not panick the kernel when it doesn't like the disk
>>> setup.
>>
>> IMO it shouldn't panic. Could it be there's more to this message than
>> you're divulging?
>
> Well, that happens if you post too late. The problem is (see a)) that it
> does not automatically start, or rather, it tries but immediately
> panicks. And vinum read panicks the system, as does vinum start.
vinum(4) contains information about how to handle panics in vinum. So
does http://www.lemis.com/vinum/how-to-debug.html. If you're having
that kind of problem, I want to know about it.
Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
