Sascha Wildner wrote:
When I try your example now, I get:
# cat vinum.conf
drive d1 device /dev/vkd1a
drive d2 device /dev/vkd2a
drive d3 device /dev/vkd3a
drive d4 device /dev/vkd4a
# vinum create -f vinum.conf
Can't open /dev/vinum/controld: No such file or directory
1: drive d1 device /dev/vkd1a
** 1 Can't initialize drive d1: Operation not supported by device
2: drive d2 device /dev/vkd2a
** 2 Can't initialize drive d2: Operation not supported by device
3: drive d3 device /dev/vkd3a
** 3 Can't initialize drive d3: Operation not supported by device
4: drive d4 device /dev/vkd4a
** 4 Can't initialize drive d4: Operation not supported by device
rm: /dev/vinum: Directory not empty
Can't create /dev/vinum/controld: File exists
0 drives:
0 volumes:
0 plexes:
0 subdisks:
Heh, some of those messages were due to me accidentally running two
vkernels using the same disk image.
Here's the correct output:
# vinum create -f vinum.conf
1: drive d1 device /dev/vkd1a
** 1 Can't initialize drive d1: Operation not supported by device
2: drive d2 device /dev/vkd2a
** 2 Can't initialize drive d2: Operation not supported by device
3: drive d3 device /dev/vkd3a
** 3 Can't initialize drive d3: Operation not supported by device
4: drive d4 device /dev/vkd4a
** 4 Can't initialize drive d4: Operation not supported by device
Can't open /dev/vinum/controld: No such file or directory
0 drives:
0 volumes:
0 plexes:
0 subdisks:
Sascha
--
http://yoyodyne.ath.cx
