problem adding subdisk to vinum

Shawn Ostapuk flagg at slumber.org
Mon Aug 11 21:40:36 PDT 2003


I have an unusual (or at least usual problem for me) with vinum that
I seem to be the only one suffering from.

I'm running freebsd 4.8 RELEASE, generic kernel...

I have about 10 drives making a terabyte or so with a simple concat
using vinum. Normally whenever i add a new drive i just do the usual:

fdisk drive, disklabel -e drive, copy c: to e: change type to vinum
then edit vinum.conf from...

drive vinumdrive0 device /dev/ad1e
drive vinumdrive1 device /dev/ad2e
drive vinumdrive2 device /dev/ad3e
drive vinumdrive3 device /dev/ad8e
drive vinumdrive4 device /dev/ad9e
drive vinumdrive5 device /dev/ad10e
drive vinumdrive6 device /dev/ad11e
drive vinumdrive7 device /dev/ad6e
drive vinumdrive8 device /dev/ad4e
drive vinumdrive9 device /dev/ad5e
volume pr0n
 plex name vinum0.p0 org concat
	sd name vinum0.p0.s0 drive vinumdrive0 size 0
	sd name vinum0.p0.s1 drive vinumdrive1 size 0
	sd name vinum0.p0.s2 drive vinumdrive2 size 0
	sd name vinum0.p0.s3 drive vinumdrive3 size 0
	sd name vinum0.p0.s4 drive vinumdrive4 size 0
	sd name vinum0.p0.s5 drive vinumdrive5 size 0
	sd name vinum0.p0.s6 drive vinumdrive6 size 0
	sd name vinum0.p0.s7 drive vinumdrive7 size 0
	sd name vinum0.p0.s8 drive vinumdrive8 size 0
	sd name vinum0.p0.s9 drive vinumdrive9 size 0
to

drive vinumdrive0 device /dev/ad1e
drive vinumdrive1 device /dev/ad2e
drive vinumdrive2 device /dev/ad3e
drive vinumdrive3 device /dev/ad8e
drive vinumdrive4 device /dev/ad9e
drive vinumdrive5 device /dev/ad10e
drive vinumdrive6 device /dev/ad11e
drive vinumdrive7 device /dev/ad6e
drive vinumdrive8 device /dev/ad4e
drive vinumdrive9 device /dev/ad5e
drive vinumdrive10 device /dev/ad7e
volume pr0n
 plex name vinum0.p0 org concat
	sd name vinum0.p0.s0 drive vinumdrive0 size 0
	sd name vinum0.p0.s1 drive vinumdrive1 size 0
	sd name vinum0.p0.s2 drive vinumdrive2 size 0
	sd name vinum0.p0.s3 drive vinumdrive3 size 0
	sd name vinum0.p0.s4 drive vinumdrive4 size 0
	sd name vinum0.p0.s5 drive vinumdrive5 size 0
	sd name vinum0.p0.s6 drive vinumdrive6 size 0
	sd name vinum0.p0.s7 drive vinumdrive7 size 0
	sd name vinum0.p0.s8 drive vinumdrive8 size 0
	sd name vinum0.p0.s9 drive vinumdrive9 size 0
	sd name vinum0.p0.s10 drive vinumdrive10 size 0

Pretty straight forward, -- this is how i added the last 4 drives or so.

run vinum create -f /etc/vinum.conf 

vinum list shows the drives all up and fine. new drive is at the end and
all the numbers add up accordingly.

BUT, now i cant mount the old filesystem

mount says invalid superblock, fsck says cant read block (and -b32,
says same thing, ad nauseum), and growfs also errors out.

if i rebuild vinum off the old configure, my filesystem is back, i can
mount it everything is okay. rebuild config with new drive, same
problem. i've resetconfig more times than i should be admitting (its
always worked fine for me in the past as long as i have my vinum.conf
file to rebuild it with). i've even tried blowing away the old config,
just doing a vinum> concat -v /dev/ad1e .. /dev/ad7e manually, if i do
it without the new drive (ad7e) it works, if i add that ad7e, i lose the
filesystem on the existing vinum partition.

from what i gathered appending a drive to the existing vinum config
should not have any effect on the existing filesystem size/data, etc. i
should be able to at the very least access it without any problems i
believe.

if anyone has any clue what is going on here or if i've found a bug i'd
appreciate it. i've racked my brain here and havent found anyone else
with the problem.

shawn.


More information about the freebsd-questions mailing list