Re: Vinum problems on 5.1 beta

----- Original Message ----- 
From: "Greg 'groggy' Lehey" <grog_at_freebsd.org>
> On Thursday, 22 May 2003 at 16:33:27 +0200, Willem Jan Withagen wrote:
> > Vinum does not seem to want to read its config.
> > # uname -a
> > FreeBSD  5.1-BETA FreeBSD 5.1-BETA #14: Sun May 18 06:02:15 CEST 2003
> > root_at_fre
> > ebee.digiware.nl:/mnt2/obj/usr/src5/sys/GENERIC  i386
> > # vinum read /dev/ad4s1h
> > Can't save Vinum config: Invalid argument
> > ** /ad4 : Unknown error: 1986356271
> >
> > # vinum read ad4
> > Can't save Vinum config: Invalid argument
> > ** : Unknown error: 540304481
> > # vinum dumpconfig
> > Drive vinumdrive0:      Device /dev/ad4s1h
> >                 Created on  at Sun Dec 29 21:52:46 2002
> >                 Config last updated Thu Apr  3 13:43:00 2003
> >                 Size:       6096786944 bytes (5814 MB)
> > volume vinum0 state up
> > plex name vinum0.p0 state up org raid5 558s vol vinum0
> > sd name vinum0.p0.s0 drive vinumdrive0 plex vinum0.p0 len 119077200s
driv=
> eoffset 265s state up plexoffset 0s
> > sd name vinum0.p0.s1 drive vinumdrive1 plex vinum0.p0 len 119077200s
driv=
> eoffset 265s state up plexoffset 558s
> > sd name vinum0.p0.s2 drive vinumdrive2 plex vinum0.p0 len 119077200s
driv=
> eoffset 265s state up plexoffset 1116s
> > sd name vinum0.p0.s3 drive vinumdrive3 plex vinum0.p0 len 119077200s
driv=
> eoffset 265s state up plexoffset 1674s
> >
> > Drive /dev/ad4s1h: 56 GB (60967840256 bytes)
>
> It's not clear from what you've said that Vinum hasn't read its
> config.  It's complaining about not being able to save it, and the
> last update date suggests that this is a correct claim.  I can't see
> anything obviously wrong with what you've sent.  Take a look at
> http://www.vinumvm.org/vinum/how-to-debug.html and look at the
> information I mention there.
>
> > [3 simular disks deleted]
> >
> > How do I get it to work again.....
>
> When did you last have it working?=20

Last time I had it working was before I upgraded, which I did because
somewhere along the lines I upgraded the kernel but not world, and did not
reboot since.
(probably got disturbed when upgrading, and forgot to complete)
So I needed to get things in sync.

I was looking for that page, but in my frustration I was nog able to find
it.
Its definitely going in my bookmarks this time.

--WjW