From owner-freebsd-current Fri May 19 9: 0:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 8166037BDBC for <current@freebsd.org>; Fri, 19 May 2000 09:00:56 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.9.3/8.9.3) with ESMTP id JAA39309; Fri, 19 May 2000 09:00:42 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <39256530.1FD33AA5@vpop.net> Date: Fri, 19 May 2000 09:00:48 -0700 From: Matthew Reimer <mreimer@vpop.net> Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey <grog@lemis.com> Cc: current@freebsd.org Subject: Re: Possible Vinum RAID-5 problems? (was: panic: ffs_valloc: dup alloc) References: <lists.freebsd.current.20000519075536.A31215@cicely5.cicely.de> <lists.freebsd.current.20000519182044.A47558@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > As far as soft updates goes, basically it's incompatible with Vinum, > since there's currently no way of ensuring the sequence of writes > across a number of disks. I'm thinking of ways of doing it, but they > will cause significant loss in performance. There should be no > problems as long as there isn't a crash, of course :-) Do you mean that softupdates is entirely incompatible with Vinum, or just incompatible with Vinum's RAID5? Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message