vinum panic on -devel

[Matthew Dillon]

:hey,
:
:as rumko already mentioned on the irc channel (but failed to post here), 
:there is a panic in vinum:
:
:reproduce: create new vinum volume, then try to newfs -v it.
:
:gives this backtrace:
:
:#12 0xc016496e in dev_dstrategy (dev=0xcbecdec0, bio=0xd2280368)
:     at /usr/build/src/sys/kern/kern_device.c:214
:#13 0xd61ce07d in launch_requests (rq=0x1, reviveok=0)
:     at /usr/build/src/sys/dev/raid/vinum/vinumrequest.c:437
:#14 0xd61cdeed in vinumstart (dev=0xcbed04f0, bio=0xc249e868, reviveok=0)
:     at /usr/build/src/sys/dev/raid/vinum/vinumrequest.c:305
:#15 0xd61cdc6f in vinumstrategy (dev=0xcbed04f0, bio=0xc249e830)
:     at /usr/build/src/sys/dev/raid/vinum/vinumrequest.c:174
:#16 0xc016475b in cdevsw_putport (port=0xc0310940, lmsg=0xd61e2a20)
:     at /usr/build/src/sys/kern/kern_device.c:98
:#17 0xc017f97e in lwkt_domsg (port=0xcbecdec0, msg=0xd61e2a20) at 

    I would be amazed if vinum still worked considering all the manual
    buffer cache manipulation it does.

    It should be possible to get it working again, but I couldn't create 
    a vinum configuration to save my life so if you provide one based on
    a few simple IDE disk partitions I will try to reproduce the problem.

						-Matt