From: Pavel Machek <pavel@suse.cz>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, Al Viro <viro@ftp.linux.org.uk>,
mingz@ele.uri.edu, mikado4vn@gmail.com,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: Question regarding to store file system metadata in database
Date: Tue, 21 Mar 2006 21:05:13 +0100 [thread overview]
Message-ID: <20060321200513.GC3931@elf.ucw.cz> (raw)
In-Reply-To: <4ae3c140603200713m24a5af0agd891a709286deb47@mail.gmail.com>
Hi!
> Second, I might want to give the background on which we are
> considering the possibility of storing metadata in database. We are
> currently developing a file system that allows multiple virtual
> machines to share base software environment. With our current design,
> a new VM can be deployed in several seconds by inheriting the file
> system of an existing VM. If a VM is to modify a shared file, the file
> system will do copy-on-write to gernerate a private copy for this VM.
> Thus, there could be multiple physical copies for a virtual pathname.
> Even more complicated, a physical copy could be shared by arbitrary
> subset of VMs. Now let's consider how to support this using regular
> file system. You can treat VMs as clients or users of a standard
> linux. Consider the following scenario: VM2 inherit VM1's file
> system. The physical copy for virtual file F is F.1. Then, it modified
> file F and get its private copy F.2. Now VM3 inherit VM2's file
> system. The inherit graph is as follow:
> VM1-->VM2-->VM3
>
> Now VM3 wants to access virtual file F. It has to determine the right
> physical copy. The right answer is F.2. But in the file system, we
> have F.1 and F.2. So some mapping mechanism must be devised. No matter
> how we manipulate the pathname of physical copies, several disk
> accesses seem to be required for a mapping operation. That is the
> reason we are considering database to store metadata.
Hardlinks? ext3cow (google it)?
Pavel
--
Picture of sleeping (Linux) penguin wanted...
next prev parent reply other threads:[~2006-03-21 20:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 4:48 Question regarding to store file system metadata in database Xin Zhao
2006-03-19 5:07 ` Mikado
2006-03-19 17:48 ` Xin Zhao
2006-03-19 17:58 ` Ming Zhang
2006-03-19 18:11 ` Xin Zhao
2006-03-19 18:26 ` Ming Zhang
2006-03-19 18:50 ` Xin Zhao
2006-03-19 19:47 ` Al Viro
[not found] ` <441DC2D6.4060001@societasilluminati.org>
2006-03-19 21:24 ` Ming Zhang
2006-03-20 13:09 ` Theodore Ts'o
2006-03-20 15:13 ` Xin Zhao
2006-03-20 19:36 ` Xin Zhao
2006-03-20 19:58 ` Al Viro
2006-03-20 22:53 ` Xin Zhao
2006-03-20 23:32 ` Al Viro
2006-03-20 21:08 ` Matti Aarnio
2006-03-20 22:28 ` Erez Zadok
2006-03-20 22:19 ` Theodore Ts'o
2006-03-21 6:51 ` Miklos Szeredi
2006-03-21 20:05 ` Pavel Machek [this message]
2006-03-22 15:21 ` Xin Zhao
2006-03-19 21:34 ` Ming Zhang
2006-03-20 8:30 ` Matti Aarnio
2006-03-19 23:06 ` Alan Cox
2006-03-19 23:44 ` Matthew Wilcox
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=20060321200513.GC3931@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikado4vn@gmail.com \
--cc=mingz@ele.uri.edu \
--cc=tytso@mit.edu \
--cc=uszhaoxin@gmail.com \
--cc=viro@ftp.linux.org.uk \
/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).