Date: Mon, 10 Jan 2000 11:18:33 -0600 From: "Jim C. Nasby" <jim@nasby.net> To: freebsd-stable@freebsd.org Subject: Re: vinum problem Message-ID: <20000110111833.E83528@enteract.com> In-Reply-To: <news2mail-85ccm1$p0i$2@mate.bln.innominate.de> References: <news2mail-85ccm1$p0i$2@mate.bln.innominate.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Which devices is it complaining about? I found it very easy to accidentally refer to the character/block devices (ie: /dev/vinum/raid0) at times during vinum setup instead of the raw devices (ie: /dev/vinum/rraid0). This will definitely cause some odd problems. I don't remember the step offhand where you have to use the raw device (newfs?), but if you used the block device instead you'll have to rebuild your vinum setup. On Mon, Jan 10, 2000 at 10:35:45AM +0000, Thomas Graichen wrote: > i have discovered some problems with vinum under 3.3-RELEASE - i > wanted to create a vinum stripe over two disks - everything i got > set up fine - but after setting "start_vinum" to YES - it started > on bootup but somehow trashed my whole /dev directory resulting > in things like fsck saying the the devices are not the correct > block/char type etc. - anyone else seen anything similar ? > > btw. i am using soft updates - maybe a problem of the two together ? > > t > > -- > graichen@innominate.de > innominate AG > networking people > fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Jim C. Nasby (aka Decibel!) /^\ jim@nasby.net /___\ Freelance lighting designer and database developer / | \ Member: Triangle Fraternity, Sports Car Club of America /___|___\ Give your computer some brain-candy! www.distributed.net Team #1828 Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html 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?20000110111833.E83528>