Date: Sat, 30 Nov 2002 10:26:45 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: "Marc G. Fournier" <scrappy@hub.org> Cc: freebsd-stable@freebsd.org Subject: Re: Recreating vinum device ... Message-ID: <20021129235645.GA17834@wantadilla.lemis.com> In-Reply-To: <20021128230846.P16724-100000@hub.org> References: <20021128234433.GG50205@wantadilla.lemis.com> <20021128230846.P16724-100000@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 28 November 2002 at 23:13:27 -0400, Marc G. Fournier wrote:
> On Fri, 29 Nov 2002, Greg 'groggy' Lehey wrote:
>
>> On Thursday, 28 November 2002 at 16:26:09 -0400, Marc G. Fournier wrote:
>>> On Thu, 28 Nov 2002, Marc G. Fournier wrote:
>>>
>>>>
>>>> Okay, I need to confirm this before I run it, cause if it doesn't work,
>>>> I'm royally screwed ...
>>>>
>>>> The old server, the drives on the controller I couldn't bring up had a
>>>> vinum RAID5 device on it ... I have the original config file that I used
>>>> to create that ...
>>>>
>>>> If I run 'vinum create -f <config file>' and don't run newfs, will I still
>>>> end up toasting the RAID5 array, or is this safe? What happens if I
>>>> inadvertently reversed the drives? Is there some way that I need to be
>>>> doing this that I'm not seein gin the vinum man page?
>>>
>>> Got it *wipe brow* Kudos to he who developed vinum, brow is still a
>>> wee damp, but the man page is great and figured out that create is
>>> not the way to go :)
>>
>> JOOI, what happened, and how did you fix it?
>
> We had an IBM xSeries server that FreeBSD lost its ability to recognize
> the 39160 dual channel controller that we had 14 drives sitting on ... we
> moved the hardware to another, non-IBM machine (ie. my desktop), which all
> the hardware show'd up on, but, in the excitement, we didn't think to mark
> the cables as to which channel was which, and, of course, my desktop
> didn't have the appropriate /dev/vinum devices ...
You don't need them. Vinum creates them on startup.
> now, I notice(d) that the drives appear to store their own information
> internally, which the dumpconfig was able to show up ... if I had plugged
> the channels in wrong (ie. da0 -> da7, da7 -> d0), what would have
> happened had I run 'vinum start'? would it know to arrange the drives
> properly regardless, or would I risk screwin gmy file system? ::(
It would have worked. If you look at dumpconfig, you'll notice that
each drive knows its own name:
Drive /dev/da3s4h: 4094 MB (4293563904 bytes)
Drive d: Device /dev/da4s4h
Created on monorchid.lemis.com at Wed Nov 27 17:28:04 2002
Config last updated Fri Nov 29 14:12:37 2002
Size: 4293563904 bytes (4094 MB)
volume swap state up
volume root state up
That's precisely why drives have their own names rather than using the
name of the underlying disk device.
Greg
--
See complete headers for address and phone numbers
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?20021129235645.GA17834>