Re: system freeze on "slice too large"

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

    I'm getting close to just throwing vinum away.  It makes so many bad
    assumptions about EVERYTHING I'm getting seriously pissed at it.

    vinum's automatic disk search is basically broken.  It is making
    ridiculous assumptions about disk layout instead of doing what it
    SHOULD be doing, which is to scan available media for partitions
    marked as being type 'vinum'.

    Try specifying an actual partition being used as a vinum drive and
    don't use the auto-start feature.  When I do that, e.g. when I
    do 'vinum read /dev/vn0s0d' on my test disk, it finds the saved
    configuration.

    When I try to do 'vinum start' vinum blows up my system.  Literally
    blows it up.  It is clearly leaving memory structures associated
    with the kernel that it has freed.  vinum is such a huge mess I just
    don't have any idea where the problem is occuring, but I think it
    may be related to how vinum tries to scan available disk media.

    So far the only 'slice too large' errors I've gotten occur when I
    try to do 'vinum start'.  I think it is related to vinum's insistance
    on rolling its own everything.  It constructs device numbers right out
    of the blue and then tries to use them.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>