From owner-freebsd-stable Wed Sep 15 17:37:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id E1D9015130 for ; Wed, 15 Sep 1999 17:37:26 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id TAA00211; Wed, 15 Sep 1999 19:37:24 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-89.tnt1.rac.cyberlynk.net(209.224.182.89) by peak.mountin.net via smap (V1.3) id sma000209; Wed Sep 15 19:37:19 1999 Message-Id: <3.0.3.32.19990915193638.01de52d0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 15 Sep 1999 19:36:38 -0500 To: Michael Robinson From: "Jeffrey J. Mountin" Subject: Re: Vinum performance testing... Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <199909151945.DAA17891@netrinsics.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:45 AM 9/16/99 +0800, Michael Robinson wrote: >Also, keep in mind that vinum does very little in the way of sanity checking. >It's very happy to trash your data if you tell it to do something even a >little bit unusual. Like anything it will only do what you tell it, so in a way I'm of agreement. >After getting seriously burned (fortunately, during initial system >configuration), I've sworn off vinum for any sort of critical production >use. When was this? What were you trying do? Not long back I decided to add a plex to a volume. There isn't any specific documentation or example for this. Having read the docs several dozen times over the past year made me pretty sure of how to do this. In short the first couple time ended up munging the vinum lable for the exisiting plex and "losing" my data. Since nothing was written to the volume it was possible to redo the labels. Presto! Everything was still present. Then wiped out the new plex, started over, and had the new plex running. The data synchronized much faster than I expected and hardly touched the CPU at all. In fact it didn't seem to be running a first glance. Don't see how you could get "burned" on an initial setup unless you did something wrong such as labeling the wrong drive or overwriting an existing filesystem. >Raw performance is only one factor in the equation. Ease of use would be another and vinum isn't the easiest thing to use at first, but at least the docs have come a long way and once you tinker around it isn't all that difficult. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve '86 Yamaha MaxiumX (not FBSD powered) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message