From owner-freebsd-stable  Thu Mar  2  8: 3:15 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2])
	by hub.freebsd.org (Postfix) with ESMTP id 7372A37C414
	for <stable@freebsd.org>; Thu,  2 Mar 2000 08:03:11 -0800 (PST)
	(envelope-from gritton@iserver.com)
Received: by gatekeeper.veriohosting.com; Thu, 2 Mar 2000 09:03:08 -0700 (MST)
Received: from unknown(192.168.1.110) by gatekeeper.veriohosting.com via smap (V3.1.1)
	id xma028395; Thu, 2 Mar 00 09:02:57 -0700
Received: by guppy.orem.iserver.com; Thu, 2 Mar 2000 09:02:38 -0700 (MST)
Date: Thu, 2 Mar 2000 09:02:38 -0700 (MST)
Message-ID: <200003021602.JAA12181@guppy.orem.iserver.com>
From: Jamie Gritton <gritton@iserver.com>
To: stable@freebsd.org
Subject: recent vinum changes
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

   I saw commit messages for the vinum driver, which apparantly apply only
to current.  As we've been having terrible vinum problems since we started
using it (reviving a mirror almost guarantees a panic and a destroyed
filesystem), and this is apparently fixed, I'd like to know if there are
plans to make these same changes to a stable version.
   Otherwise, I'd have to go to FreeBSD 4 ahead of it being made the
"stable" version, as I doubt all the potential instabilities in the latest
OS can stand up to the unstable vinum we have now.

- Jamie


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message