RE: gvinum startup problems

After the gvinum MFCs earlier today there has been some regression in
the RELENG_6 branch.

Starting gvinum manually works, but no device node is created (no
/dev/gvinum dir at all). This means the array cannot be used.

As before, auto-loading gvinum results in a broken array. Right after
probing the ATA disks, the following message is printed on the console:

GEOM_VINUM: subdisk 480GB.p0.s3 state change: down -> stale
GEOM_VINUM: subdisk 480GB.p0.s0 state change: down -> stale

This of course results in a broken array:

# gvinum list
4 drives:
D vd1                   State: up       /dev/ad3        A: 0/117800 MB
(0%)
D vd0                   State: up       /dev/ad2        A: 0/117800 MB
(0%)
D vd3                   State: up       /dev/ad1        A: 0/117800 MB
(0%)
D vd2                   State: up       /dev/ad0        A: 0/117800 MB
(0%)

1 volume:
V 480GB                 State: down     Plexes:       1 Size:        460
GB

1 plex:
P 480GB.p0            S State: down     Subdisks:     4 Size:        460
GB

4 subdisks:
S 480GB.p0.s3           State: stale    D: vd3          Size:        115
GB
S 480GB.p0.s2           State: up       D: vd2          Size:        115
GB
S 480GB.p0.s1           State: up       D: vd1          Size:        115
GB
S 480GB.p0.s0           State: stale    D: vd0          Size:        115
GB


Manually doing "gvinum setstate up 480GB.p0.s0" and gvinum setstate up
480GB.p0.s3" brings the array back online, and it can be used as normal
(fsck and mount).

If gvinum really is this broken, shouldn't it be removed from RELENG_6?
Or is this just something local on my setup?

Oh, and there is still no manpage for gvinum.

/Daniel Eriksson