gvinum remains broken in 5.3-RELEASE?

[Andy Farkas]

On Mon, 8 Nov 2004, Lukas Ertl wrote:

> On Tue, 9 Nov 2004, Andy Farkas wrote:
>
>> ... but my {g}vinum problem is still real..
>
> Yes, that's a very mean problem.  The problem is that the old meta-data is on 
> da4, and the new is on da4s1.  That collision is really hard to handle. My 
> advice would be:
>
> *) keep a copy of gvinum printconfig and of bsdlabel of all drives.
> *) dd if=/dev/zero of=/dev/disk to wipe out the slice table, the bsdlabel
>   and the vinum config, but be careful to only touch the first few
>   sectors.  You might want to experiment with only one sector and go up
>   until the slice table and the bsdlabel is gone.
> *) once finished with that, recreate slices as they are now plus the
>   bsdlabels that you copied, and then recreate the vinum config from what
>   you got before minus the objects that you don't want.
>
> Just make sure that you get all offsets and sizes correct, then you shouldn't 
> lose any data.
>
> The problem of old, stale metadata is one I didn't think of.  Since gvinum 
> doesn't care about the type of partition as vinum did, one might run into a 
> problem like you.
>
> thanks,
> le

I will copy the degraded volume to tape, then try your suggestion.
It will take a while, but I'll get back to you...

- andyf