Replacing failed drive in gvinum causes panic

[Ulf Lilleengen]

On Fri, Sep 15, 2006 at 07:48:57AM -0800, Peter A. Giessel wrote:
> On 2006/09/15 4:56, Ulf Lilleengen seems to have typed:
> > Do you also have a different sized drive as Ludo had?
> > The thing is, that a subdisk has a drive_offset that indicates where on the
> > drive that a subdisk begin. Gvinum may not actually handle this. 
> > 
> Do something more like:
> **************************
> # /dev/ad16s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   c: 390716802       0    unused        0     0         # "raw" part, don't edit
>   h: 390620412       0     vinum 
> 
> # /dev/ad18s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   c: 390620412        0    unused        0     0         # "raw" part, don't edit
>   h: 390620412        0     vinum 
> **************************
> Will that help problems in the future?

Hi,

How did it go? I forgot all about this as I became busy with school, sorry. 
Changing the labels shouldn't be necessary, but the drive you're replacing with
should have at least the same labelsize as the one you replacing. That could be
it, but I've not been able to test this yet because I can't forcely remove drive
in gvinum, and I don't have any real hd's to test with, but I guess I can
implement a force-flag for removal of a drive for this purpose.

This guide says more on this.
http://www.vinumvm.org/vinum/replacing-drive.html

-- 
Ulf Lilleengen