Re: delta filesystem prototype

[Nikolaus Rath <Nikolaus-BTH8mxji4b0@public.gmane.org>]

Goswin von Brederlow <goswin-v-b@web.de> writes:
> hooanon05@yahoo.co.jp writes:
>
>> Goswin von Brederlow:
>>> > 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.
>> 	:::
>>> Use a filename -> inode indirection and delta based on inode
>>> numbers. Although the you also have to consider the device id in case
>>> there are multiple filesystem mounted in your read-only branch. So
>>> filename -> (dev, inode).
>>
>> Agreed.
>> While Miklos seems to dislike the inum table, it is necessary I think.
>
> Only if you want to fully support hardlinks. Do you know of anything
> that really needs true hardlinks?

storeBackup, for example (but I guess that's nothing you'd run on a
unionfs). 


Best,

   -Nikolaus

-- 
 »Time flies like an arrow, fruit flies like a Banana.«

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
fuse-devel mailing list
fuse-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fuse-devel