Date: Fri, 19 May 2000 12:43:28 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Matthew Reimer <mreimer@vpop.net> Cc: Greg Lehey <grog@lemis.com>, current@FreeBSD.ORG Subject: Re: Possible Vinum RAID-5 problems? (was: panic: ffs_valloc: dup alloc) Message-ID: <200005191943.MAA40388@apollo.backplane.com> References: <lists.freebsd.current.20000519075536.A31215@cicely5.cicely.de> <lists.freebsd.current.20000519182044.A47558@freebie.lemis.com> <39256530.1FD33AA5@vpop.net>
next in thread | previous in thread | raw e-mail | index | archive | help
: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
Wait a sec... softupdates does not depend on write ordering. Softupdates
issues all non-conflicting writes in parallel and doesn't care what order
they are written to the disk. When those complete, softupdates will then
followup with all the writes that depend on the original set.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005191943.MAA40388>