From: Goswin von Brederlow <goswin-v-b@web.de>
To: hooanon05@yahoo.co.jp
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
Miklos Szeredi <miklos@szeredi.hu>,
bs_lists@aakef.fastmail.fm, fuse-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [fuse-devel] delta filesystem prototype
Date: Mon, 09 Mar 2009 13:28:57 +0100 [thread overview]
Message-ID: <87y6vex4l2.fsf@frosties.localdomain> (raw)
In-Reply-To: <8773.1236417375@jrobl> (hooanon's message of "Sat, 07 Mar 2009 18:16:15 +0900")
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.
>
>
> J. R. Okajima
Only if you want to fully support hardlinks. Do you know of anything
that really needs true hardlinks?
MfG
Goswin
next prev parent reply other threads:[~2009-03-09 12:29 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 14:42 delta filesystem prototype Miklos Szeredi
2009-02-28 17:22 ` [fuse-devel] " Goswin von Brederlow
2009-03-01 0:38 ` Bernd Schubert
2009-03-01 10:17 ` Goswin von Brederlow
2009-03-04 11:21 ` Miklos Szeredi
2009-03-04 14:12 ` Goswin von Brederlow
2009-03-05 13:06 ` Miklos Szeredi
2009-03-05 19:58 ` Goswin von Brederlow
2009-03-06 4:10 ` hooanon05
2009-03-06 12:37 ` Goswin von Brederlow
2009-03-07 1:16 ` hooanon05
2009-03-07 9:01 ` Goswin von Brederlow
2009-03-07 9:12 ` hooanon05
2009-03-09 12:21 ` Goswin von Brederlow
2009-03-09 13:35 ` hooanon05
2009-03-09 14:22 ` Goswin von Brederlow
2009-03-09 15:25 ` hooanon05
2009-03-10 8:14 ` Goswin von Brederlow
2009-03-09 16:36 ` Miklos Szeredi
2009-03-06 11:35 ` Miklos Szeredi
2009-03-06 12:50 ` Goswin von Brederlow
2009-03-06 13:21 ` Miklos Szeredi
2009-03-07 8:56 ` Goswin von Brederlow
2009-03-07 1:19 ` hooanon05
2009-03-07 9:03 ` Goswin von Brederlow
2009-03-07 9:16 ` hooanon05
2009-03-09 12:28 ` Goswin von Brederlow [this message]
2009-03-09 13:36 ` hooanon05
2009-03-09 14:25 ` Goswin von Brederlow
2009-03-09 15:20 ` hooanon05
2009-03-10 8:06 ` Goswin von Brederlow
2009-03-10 8:44 ` hooanon05
2009-03-12 9:22 ` Tomas M
2009-03-12 9:40 ` Goswin von Brederlow
2009-03-12 9:19 ` Tomas M
2009-03-09 14:13 ` Nikolaus Rath
2009-03-03 8:31 ` hooanon05
2009-03-03 10:59 ` [fuse-devel] " Goswin von Brederlow
2009-03-03 13:11 ` hooanon05
2009-03-03 15:27 ` Dave Kleikamp
2009-03-03 15:50 ` hooanon05
2009-03-03 15:54 ` Dave Kleikamp
2009-03-03 16:02 ` hooanon05
2009-03-03 16:14 ` Dave Kleikamp
2009-03-03 16:19 ` hooanon05
2009-03-03 16:46 ` Dave Kleikamp
2009-03-03 17:13 ` hooanon05
2009-03-04 11:52 ` Goswin von Brederlow
2009-03-04 14:10 ` Dave Kleikamp
2009-03-04 16:23 ` hooanon05
2009-03-04 11:49 ` Goswin von Brederlow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6vex4l2.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=bs_lists@aakef.fastmail.fm \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).