From owner-freebsd-stable Sat Sep 18 18:37: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id 14E6E15116 for ; Sat, 18 Sep 1999 18:36:49 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (robinson@[202.106.228.139]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id JAA19856 for ; Sun, 19 Sep 1999 09:31:19 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id JAA00550; Sun, 19 Sep 1999 09:33:00 +0800 (CST) (envelope-from robinson) Date: Sun, 19 Sep 1999 09:33:00 +0800 (CST) From: Michael Robinson Message-Id: <199909190133.JAA00550@netrinsics.com> To: dcs@newsguy.com Subject: Re: Vinum performance testing... Cc: freebsd-stable@freebsd.org In-Reply-To: <37E3D23A.48381641@newsguy.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: >Err, Michael, from your description of what happened, it seems >rather that you issued commands that resulted in the trashing. So, >it was rather a lack of banisters than a bug in the software. That's >a rather different case, imho. Not just a lack of banisters, but a lack of documentation of the lack of banisters. There's nothing in the documentation that says you have to "read" all subdisks of a striped plex in one command, or else you will trash the plex. And banisters are extremely important in 24x7 production environments. In my experience, downtime caused by operator intervention is more common than downtime caused by mechanical failure. So, while a flawless vinum installation may well be possible, it is still far too fragile at this point for me to bet the business on it. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message