From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: Re: srfs - a new file system. Date: 23 Oct 2003 14:12:25 -0600 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1066939945.11997.38.camel@patehci2> References: <20031022142213.GA5037@delft.aura.cs.cmu.edu> <20031023123357.GB1465@vagabond> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: tzachar@cs.bgu.ac.il, jaharkes@cs.cmu.edu, linux-fsdevel@vger.kernel.org Return-path: Received: from email-out1.iomega.com ([147.178.1.82]:57051 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S261782AbTJWUMm (ORCPT ); Thu, 23 Oct 2003 16:12:42 -0400 To: bulb@ucw.cz In-Reply-To: <20031023123357.GB1465@vagabond> List-Id: linux-fsdevel.vger.kernel.org > > transient errors can and will happen. so, a cosmic ray can hit N out > > of your 2N+1 hosts, and corrupt the data they hold. its very slim, > > but you have to take these kind of errors into > > account to prove the correctness of the algorithm. > > But the vector time approach solves this too and does so a lot better. > > If we return to the example with notebook ... > Now, with vector time, the system decides, that > * All copies in the lab are old and invalidates them. > * Our copies conflict. It does not blindly choose one, > rather it asks for assistance. We regard getting everyone to agree about what the time is as a solved problem? I'm inspired to ask because I'm posting this query from behind an employer-owned firewall thru which I have not yet punched time service, cvs, etc. There was a day, not so long ago, when I couldn't punch thru ftp and streaming media ... Pat LaVarre