From mboxrd@z Thu Jan 1 00:00:00 1970 From: Erik Andersen Subject: Re: srfs - a new file system. Date: Tue, 21 Oct 2003 22:57:09 -0600 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20031022045708.GA5636@codepoet.org> References: Reply-To: andersen@codepoet.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from codepoet.org ([166.70.99.138]:50861 "EHLO codepoet.org") by vger.kernel.org with ESMTP id S263411AbTJVE5G (ORCPT ); Wed, 22 Oct 2003 00:57:06 -0400 To: Nir Tzachar Content-Disposition: inline In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org On Mon Oct 20, 2003 at 11:12:07AM +0200, Nir Tzachar wrote: > more info on the system architecture can be find on the web page, and > here: http://www.cs.bgu.ac.il/~tzachar/srfs.pdf Suppose I install srfs on both my laptop and my server. I then move the CVS repository for my pet project onto the new srfs filesystem and I take off for the weekend with my laptop. Over the weekend I commit several changes to file X. Over the weekend my friend also commits several changes to file X. When I get home and plug in my laptop, presumably the caching daemon will try to stabalize the system by deciding which version of file X was changed last and replicating that latest version. Who's work will the caching daemon overwrite? My work, or my friends work? Of course, this need not involve anything so extreme as days of disconnected independent operation. A rebooting router between two previously syncd srfs peers seems sufficient to trigger this kind of data loss, unless you make the logging daemon fail all writes when disconnected. -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons--