From owner-freebsd-fs@FreeBSD.ORG Wed Feb 3 14:53:40 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 558FB1065694 for ; Wed, 3 Feb 2010 14:53:40 +0000 (UTC) (envelope-from lopez.on.the.lists@yellowspace.net) Received: from mail.yellowspace.net (mail.yellowspace.net [80.190.200.164]) by mx1.freebsd.org (Postfix) with ESMTP id C7F3A8FC08 for ; Wed, 3 Feb 2010 14:53:39 +0000 (UTC) Received: from furia.intranet ([93.104.43.176]) (AUTH: LOGIN lopez.on.the.lists@yellowspace.net) by mail.yellowspace.net with esmtp; Wed, 03 Feb 2010 15:53:37 +0100 id 0036A185.000000004B698DF1.000022D2 Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Lorenzo Perone In-Reply-To: <20100128132613.olxiwcq0go0g0w88@www.hmallett.co.uk> Date: Wed, 3 Feb 2010 15:53:37 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <9B1DF836-0CCC-4CB2-B83C-3040428A7344@yellowspace.net> References: <914E8A1F-2FE9-4A7E-9BC7-6174402B57D3@yellowspace.net> <20100128132613.olxiwcq0go0g0w88@www.hmallett.co.uk> To: Hywel Mallett X-Mailer: Apple Mail (2.1077) Cc: freebsd-fs@freebsd.org Subject: Re: Any news on the HAST Project? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2010 14:53:40 -0000 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