Date: Wed, 3 Feb 2010 15:53:37 +0100 From: Lorenzo Perone <lopez.on.the.lists@yellowspace.net> To: Hywel Mallett <hywel@hmallett.co.uk> Cc: freebsd-fs@freebsd.org Subject: Re: Any news on the HAST Project? Message-ID: <9B1DF836-0CCC-4CB2-B83C-3040428A7344@yellowspace.net> In-Reply-To: <20100128132613.olxiwcq0go0g0w88@www.hmallett.co.uk> References: <914E8A1F-2FE9-4A7E-9BC7-6174402B57D3@yellowspace.net> <20100128132613.olxiwcq0go0g0w88@www.hmallett.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28.01.2010, at 14:26, Hywel Mallett wrote: > About the same time a status update was posted on the FreeBSD = Foundation blog at = http://freebsdfoundation.blogspot.com/2009/12/update-on-hast-project.html Thanx, also to pjd's answer. That gives some nice insight already. Great = work! HAST could in fact change radically the way of using block devices = and distributing mass storage. I look forward to testing it first on a = few vboxes and shortly thereafter on real machines.=20 Really curious on how several things are implemented, e.g. performance / = latency / fail / sync issues (what happens for example when a big huge = file is written locally on a very fast primary, and there is not enough = ram to buffer it before sending it to a secondary.. etc, scenarios like = that).=20 And how well it will do with ZFS too: although ZFS has its 'own' HAST = via send/recv (and besides might get its own implementation for some = sort of 'streaming' send/recv..) it is also true that it'd allow for = some great flexibility in creating primary/secondary volumes (zvols). = Just imagining a scenario with sparse zvols and HAST disting them = around.. ok ok I stop here :-) Greets && Regards, Lorenzo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9B1DF836-0CCC-4CB2-B83C-3040428A7344>