From owner-freebsd-stable Mon Jan 10 2:52:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [212.84.196.35]) by hub.freebsd.org (Postfix) with ESMTP id C53AA14CB9 for ; Mon, 10 Jan 2000 02:52:43 -0800 (PST) (envelope-from news-list.freebsd.stable@innominate.de) Received: from mate.bln.innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with ESMTP id LAA17016 for ; Mon, 10 Jan 2000 11:52:41 +0100 Received: by mate.bln.innominate.de (Postfix, from userid 9) id D84D72CA6E; Mon, 10 Jan 2000 11:35:46 +0100 (CET) From: news-list.freebsd.stable@innominate.de (Thomas Graichen) Reply-To: Thomas Graichen X-Newsgroups: innominate.bln.list.freebsd.stable Subject: vinum problem Date: 10 Jan 2000 10:35:45 GMT Organization: innominate AG, Berlin, Germany Lines: 16 Message-ID: Reply-To: graichen@innominate.de X-Trace: mate.bln.innominate.de 947500545 25618 10.0.0.13 (10 Jan 2000 10:35:45 GMT) X-Complaints-To: news@innominate.de User-Agent: tin/pre-1.4-19990805 ("Preacher Man") (UNIX) (FreeBSD/4.0-CURRENT (i386)) To: stable@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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