From owner-freebsd-stable Thu Mar 2 10:40:10 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 3789537C230 for ; Thu, 2 Mar 2000 10:40:01 -0800 (PST) (envelope-from gritton@iserver.com) Received: by gatekeeper.veriohosting.com; Thu, 2 Mar 2000 11:40:00 -0700 (MST) Received: from unknown(192.168.1.110) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma000636; Thu, 2 Mar 00 11:39:50 -0700 Received: by guppy.orem.iserver.com; Thu, 2 Mar 2000 11:39:30 -0700 (MST) To: stable@freebsd.org Subject: Re: recent vinum changes References: <200003021602.JAA12181@guppy.orem.iserver.com> From: Jamie Gritton Date: 02 Mar 2000 11:39:30 -0700 In-Reply-To: Brad Knowles's message of "Thu, 2 Mar 2000 19:29:47 +0100" Message-ID: Lines: 26 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles writes: > the last word I heard from Greg were that he was concentrating all > his work on 4.0-CURRENT, and it didn't sound like anything was likely > to get back-ported to -STABLE. > That said, mirroring under -STABLE should be pretty rock-solid... That's unfortunate, given the comment he included in the vinumrevive.c log: | Fix horrible, embarrassing breakage which caused occasional panics and | data corruption. It's a wonder it worked at all. I think this indicates that the mirroring currently under -STABLE is anything but rock-solid. > ...and if you can show him a case where it bombs, I would assume that he > would be inclined to try to work out the bug and the fix for it, > which should then get incorporated into future versions of -STABLE. We've sent such already, and it matches the log comment. What can I say, but that I've been experiencing regular panics and complete data obliteration anytime I needed to revive a vinum mirror? - Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message