From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <01e65e0d82a93d02f36fe3c98b76ae41@coraid.com> References: <20100111082753.BA91311803D@smtp.hushmail.com> <20100111140745.GA21294@endeavour> <126f64914bf395ab797aa58afc6344e6@coraid.com> <20100111165440.GA21617@endeavour> <01e65e0d82a93d02f36fe3c98b76ae41@coraid.com> From: Venkatesh Srinivas Date: Mon, 11 Jan 2010 12:29:37 -0500 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Hardware for Plan9 Topicbox-Message-UUID: bd3006ec-ead5-11e9-9d60-3106f5b1d025 On Mon, Jan 11, 2010 at 12:24 PM, erik quanstrom wrot= e: >> Venti deals with incompletely written blocks; the arenas and index struc= tures >> are still workable. The situation is even recoverable - a proxy could no= tice >> that one of the backends failed to return a read, so it rewrite the data= from >> an other copy (which it can verify) to the failed one. > > what are you using as a venti proxy? =C2=A0or is this more theoretical? When I ran this on real h/w, I used Inferno's vcache, which works as-is. I have a binary (but have lost the source) for a Plan 9 equivalent, but cooking one up again should take only a few hours; its job is really simple. > how do you protect against lossage in the fossil cache? I don't, any more than fossil+fs does. > - erik -- vs