Vinum configuration lost at vinum stop / start

[Kim Helenius]

Greetings. I posted earlier about problems with vinum raid5 but it 
appears it's not restricted to that:

Let's make a fresh start with vinum resetconfig. Then vinum create 
kala.txt which contains:

drive d1 device /dev/ad4s1d
drive d2 device /dev/ad5s1d
volume vinum0
plex org concat
sd length 586096s drive d1
sd length 586096s drive d2

Output:

2 drives:
D d1                    State: up       /dev/ad4s1d     A: 285894/286181 
MB (99%)
D d2                    State: up       /dev/ad5s1d     A: 285894/286181 
MB (99%)

1 volumes:
V vinum0                State: up       Plexes:       1 Size:        572 MB

1 plexes:
P vinum0.p0           C State: up       Subdisks:     2 Size:        572 MB

2 subdisks:
S vinum0.p0.s0          State: up       D: d1           Size:        286 MB
S vinum0.p0.s1          State: up       D: d2           Size:        286 MB

Now I can newfs /dev/vinum/vinum0, mount it, use it, etc. But when I do 
vinum stop, vinum start, vinum stop, and vinum start something amazing 
happens. Vinum l after this is as follows:

2 drives:
D d2                    State: up       /dev/ad5s1d     A: 286181/286181 
MB (100%)
D d1                    State: up       /dev/ad4s1d     A: 286181/286181 
MB (100%)

0 volumes:
0 plexes:
0 subdisks:

Where did my configuration go?! I can of course recreate it, with no 
data lost, but imagine this on a raid5 where the plex goes into init 
mode after creation. Not a pleasant scenario. Also recreating the 
configuration from a config file after every reboot doesn't sound 
interesting.

-- 
Kim Helenius
tristan at cc.jyu.fi