From mboxrd@z Thu Jan 1 00:00:00 1970 From: hooanon05@yahoo.co.jp Subject: Re: [fuse-devel] delta filesystem prototype Date: Fri, 06 Mar 2009 13:10:18 +0900 Message-ID: <7231.1236312618@jrobl> References: <87sklyh3wu.fsf@frosties.localdomain> <200903010138.39329.bs_lists@aakef.fastmail.fm> <87eixhfsyi.fsf@frosties.localdomain> <87y6vlcr6p.fsf@frosties.localdomain> <87mybzd9nn.fsf@frosties.localdomain> Cc: Miklos Szeredi , bs_lists@aakef.fastmail.fm, fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org To: Goswin von Brederlow Return-path: Received: from vsmtp03.dti.ne.jp ([202.216.231.138]:64603 "EHLO vsmtp03.dti.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753203AbZCFEKm (ORCPT ); Thu, 5 Mar 2009 23:10:42 -0500 In-Reply-To: <87mybzd9nn.fsf@frosties.localdomain> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Goswin von Brederlow: > The problem is that /delta-fs/path/file would suddenly be a composite > of the new file /union/read-only/path/file and any stored delta > information in /union/read-write/path/file of the old file. Yes. And I am afraid stat.st_blocks will be incorrect too. But it may be a smaller problem for who think there is another bigger advantage. It might be just a trade off. J. R. Okajima