Date: Sat, 2 Jun 2001 12:13:53 -0500 From: Steve Price <steve@havk.org> To: freebsd-stable@freebsd.org Subject: vinum panic Message-ID: <20010602121353.N688@bsd.havk.org>
next in thread | raw e-mail | index | archive | help
I've been trying for several days now to get a RAID5 volume
setup on a new box and no matter what I've tried it always
ends up panic'ing the kernel where I try to create the volume.
Here's my configuration file:
drive d1 device /dev/da1s1e
drive d2 device /dev/da2s1e
drive d3 device /dev/da3s1e
drive d4 device /dev/da4s1e
drive d5 device /dev/da5s1e
volume raid
plex org raid5 512k
sd length 17626m drive d1
sd length 17626m drive d2
sd length 17626m drive d3
sd length 17626m drive d4
sd length 17626m drive d5
I've decided that I would skip RAID5 and do RAID10 instead
because I've had success with it before. So after the crash
here's what I did.
vinum
vinum -> resetconfig
vinum -> saveconfig
vinum -> stop
newfs /dev/da1s1e
newfs /dev/da2s1e
newfs /dev/da3s1e
newfs /dev/da4s1e
newfs /dev/da5s1e
disklabel -e /dev/da1s1e # change 4.2BSD to vinum for 'e'
disklabel -e /dev/da2s1e
disklabel -e /dev/da3s1e
disklabel -e /dev/da4s1e
disklabel -e /dev/da5s1e
vinum
vinum -> mirror -v -n raid10 -s /dev/da2s1e /dev/da3s1e /dev/da4s1e /dev/da5s1e
drive vinumdrive0 device /dev/da2s1e
vinum: drive vinumdrive0 is up
Can't create drive vinumdrive0, device /dev/da2s1e: Invalid argument (22)
vinum -> printconfig
# Vinum configuration of , saved at Sat Jun 2 07:09:00 2001
vinum -> ls
vinum -> ld
vinum -> lv
vinum -> lp
vinum -> quit
How can vinumdrive0 be up when it isn't defined? Anyone have
any pointers to help down the road to vinum nirvana?
Thanks.
-steve
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010602121353.N688>