Date: Tue, 9 Nov 2004 01:23:37 +1100 (EST) From: Andy Farkas <andy@bradfieldprichard.com.au> To: Lukas Ertl <le@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: gvinum remains broken in 5.3-RELEASE? Message-ID: <20041109012152.R59522@bpgate.speednet.com.au> In-Reply-To: <20041108142458.J5398@pcle2.cc.univie.ac.at> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de> <20041108084037.O570@korben.prv.univie.ac.at> <20041108120226.L5398@pcle2.cc.univie.ac.at> <20041108141311.M5398@pcle2.cc.univie.ac.at> <20041108142458.J5398@pcle2.cc.univie.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041109012152.R59522>