Replacing failed drive in gvinum causes panic

[Peter A. Giessel]

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. 
> 


*slightly*  Original configuration:

-------------------------------
6 drives:
D one                   State: up	/dev/ad18s1	A: 0/190732 MB (0%)
D eleven                State: up	/dev/ad16s1	A: 47/190779 MB (0%)
D two                   State: up	/dev/ad14s1	A: 0/190732 MB (0%)
D three                 State: up	/dev/ad12s1	A: 47/190779 MB (0%)
D four                  State: up	/dev/ad11s1	A: 47/190779 MB (0%)
D five                  State: up	/dev/ad10s1	A: 47/190779 MB (0%)
--------------------------------

As you can see, they vary from 190732 MB to 190779 MB, a difference of
47 MB.

Am I understanding you correctly to say that I should adjust the slices
so that all their slices are the same?

instead of:
**************************
# /dev/ad16s1:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 390716802       0    unused        0     0         # "raw" part, don't edit
  h: 390716802       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 
**************************

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?