From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Saket Sinha <saket.sinha89@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM ATTEND] Stackable Union Filesystem Implementation
Date: Wed, 08 Jan 2014 14:10:09 +0900 [thread overview]
Message-ID: <6469.1389157809@jrobl> (raw)
In-Reply-To: <CAK25hWMdfSmZLZQugJ3YU=b6nb7ZQzQFw514e=HV91s0Z-W0nQ@mail.gmail.com>
Saket Sinha:
> Several implementations of union file system fusion were evaluated.
> The results of the evaluation is shown at the below link-
> http://www.4shared.com/download/7IgHqn4tce/1_online.png
As far as I know, aufs supports NFS branches and also you can export
aufs via NFS.
For example,
http://sourceforge.net/p/aufs/mailman/message/20639513/
> 2. if only the file metadata are modified, then do not
> copy the whole file on the read-write files system but
> only the metadata (stored with a file named as the file
> itself prefixed by '.me.')
Once I have considered such approach to implement it in aufs.
But I don't think it a good idea to store metadata in multiple places,
one in the original file and the other is in .me. file.
For such purpose, a "block device level union" (instead of filesystem
level union) may be an option for you, such as "dm snapshot".
J. R. Okajima
WARNING: multiple messages have this Message-ID (diff)
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Saket Sinha <saket.sinha89@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM ATTEND] Stackable Union Filesystem Implementation
Date: Wed, 08 Jan 2014 14:10:09 +0900 [thread overview]
Message-ID: <6469.1389157809@jrobl> (raw)
In-Reply-To: <CAK25hWMdfSmZLZQugJ3YU=b6nb7ZQzQFw514e=HV91s0Z-W0nQ@mail.gmail.com>
Saket Sinha:
> Several implementations of union file system fusion were evaluated.
> The results of the evaluation is shown at the below link-
> http://www.4shared.com/download/7IgHqn4tce/1_online.png
As far as I know, aufs supports NFS branches and also you can export
aufs via NFS.
For example,
http://sourceforge.net/p/aufs/mailman/message/20639513/
> 2. if only the file metadata are modified, then do not
> copy the whole file on the read-write files system but
> only the metadata (stored with a file named as the file
> itself prefixed by '.me.')
Once I have considered such approach to implement it in aufs.
But I don't think it a good idea to store metadata in multiple places,
one in the original file and the other is in .me. file.
For such purpose, a "block device level union" (instead of filesystem
level union) may be an option for you, such as "dm snapshot".
J. R. Okajima
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-01-08 5:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 10:34 [LSF/MM ATTEND] Stackable Union Filesystem Implementation Saket Sinha
2014-01-07 12:23 ` Jan Kara
2014-01-07 20:04 ` Saket Sinha
2014-01-08 5:10 ` J. R. Okajima [this message]
2014-01-08 5:10 ` J. R. Okajima
2014-01-08 18:06 ` Saket Sinha
2014-01-09 7:32 ` J. R. Okajima
2014-01-09 7:32 ` J. R. Okajima
2014-01-09 9:19 ` Saket Sinha
2014-01-09 14:17 ` J. R. Okajima
2014-01-11 17:21 ` Saket Sinha
2014-01-08 11:16 ` Jan Kara
2014-01-08 11:16 ` Jan Kara
2014-01-08 18:26 ` Saket Sinha
2014-01-08 21:26 ` Jan Kara
2014-01-09 10:06 ` Saket Sinha
2014-01-07 16:52 ` J. R. Okajima
2014-01-07 20:21 ` Saket Sinha
-- strict thread matches above, loose matches on Subject: below --
2014-01-07 10:32 Saket Sinha
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=6469.1389157809@jrobl \
--to=hooanon05g@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=saket.sinha89@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.