From mboxrd@z Thu Jan 1 00:00:00 1970 From: hooanon05@yahoo.co.jp Subject: Re: [fuse-devel] delta filesystem prototype Date: Sat, 07 Mar 2009 10:19:46 +0900 Message-ID: <639.1236388786@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: goswin-v-b@web.de, bs_lists@aakef.fastmail.fm, fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org To: Miklos Szeredi Return-path: Received: from vsmtp04.dti.ne.jp ([202.216.231.139]:49641 "EHLO vsmtp04.dti.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752499AbZCGBUJ (ORCPT ); Fri, 6 Mar 2009 20:20:09 -0500 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Miklos Szeredi: > The most interesting is the directory and metadata deltas, which do > make a delta-fs like implementation much more effective and nicer as a > dumb union type filesystem. Mind, unionfs and aufs are rapidly > acquiring non-union traits, like inode number storage, virtual hard > links (not to speak of whiteouts). Which makes them all the more > hackish, I much prefer a conceptually clean solution. I agree that the delta is a good approach. But it is for filedata only. As I wrote in another mail, how do you support hardlinks on the lower readonly layer? J. R. Okajima