Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jun 2002 19:09:51 -0600
From:      Chris Bolt <chris-lists@bolt.cx>
To:        Greg 'groggy' Lehey <grog@FreeBSD.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: vinum problems
Message-ID:  <3D112B5F.20906@bolt.cx>
References:  <3D1051FA.8030400@bolt.cx> <20020619234522.GI29978@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>> What the? How do I fix d2?
> 
> Is it there?  Does dmesg see it?

Yes:

ad0: 57241MB <WDC WD600BB-00CAA0> [116301/16/63] at ata0-master UDMA100
ad1: 57241MB <WDC WD600BB-00CAA1> [116301/16/63] at ata0-slave UDMA100
ad2: 57241MB <WDC WD600BB-00CAA1> [116301/16/63] at ata1-master UDMA100
ad3: 57241MB <WDC WD600BB-00CAA1> [116301/16/63] at ata1-slave UDMA100

And I have the disk partitioned correctly:

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
   c: 117226242        0    unused        0     0        # (Cyl.    0 - 
7296*)
   e: 117226242        0     vinum                       # (Cyl.    0 - 
7296*)

> Please don't wrap computer output.  It changes the meaning.  There's
> no reason to be afraid of this, though it looks strange.

Okay, here's the state of the configuration from the disks:

http://www.bolt.cx/~chris/vinum/log

And a vinum list:

http://www.bolt.cx/~chris/vinum/list

How do I change d2 so it is no longer referenced, and associate 
raid5.p0.s1 with it? The man page says:

referenced 
At least one subdisk refers to the drive, but it is not
		currently accessible to the system.  No device name is
		known.

So how can I associate a device name with it? The only thing that seems 
like the closest thing to me is "vinum create" without a filename, which 
apparently allows me to edit the configuration... but that doesn't seem 
right to me, even after reading the man page 5 times over.

Should I be creating another drive with a different name? I tried that, 
but it still seems to be associated with the old invalid drive, and the 
attach command only allows me to attach a plex to a volume, or a subdisk 
to a plex, not a subdisk to a drive.

>>Any ideas?
> 
> Yes.  They're at http://www.vinumvm.org/vinum/how-to-debug.html and in
> the man pages.

Okay. I'm using FreeBSD 4.5-RELEASE. I haven't changed any sources.

Here's vinum_history: http://www.bolt.cx/~chris/vinum/vinum_history
and /var/log/messages: http://www.bolt.cx/~chris/vinum/messages

BTW, there is a typo in man 8 vinum:

LOG FILE
	vinum maintains a log file, by default /var/tmp/vinum_history,
	in which it keeps track of the commands issued to vinum.

> Greg
> --
> See complete headers for address and phone numbers

-- 
Chris Bolt
chris@bolt.cx
http://www.bolt.cx/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




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