From: Al Boldi <a1426z@gawab.com>
To: "Eric Van Hensbergen" <ericvh@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] VFS: FS CoW using redirection
Date: Sun, 9 Jul 2006 15:50:36 +0300 [thread overview]
Message-ID: <200607091550.36407.a1426z@gawab.com> (raw)
In-Reply-To: <a4e6962a0607081132u4558473cgf89b8b25fcea317d@mail.gmail.com>
Eric Van Hensbergen wrote:
> On 7/8/06, Al Boldi <a1426z@gawab.com> wrote:
> > Copy on Write is a neat way to quickly achieve a semi-clustered system,
> > by mounting any shared FS read-only and redirecting writes to some
> > perClient FS.
> >
> > Would this redirection be easy to implement into the VFS?
>
> There are a variety of solutions that have been proposed or are
> available to do this sort of thing. You may want to start by looking
> at unionfs and mapfs. There are also folks looking at doing this from
> the block layer (look at the dm-userspace + cowd as well as evms and
> lvm snapshots).
The idea here, is to do things completely transparent while being as
unintrusive as possible, by relying on the current FS infrastructure, w/o
introducing another VFS.
Consider something simple like this:
VFS - anyFS1 (r/w) used normally, unless ENotFound, then redirect read to
\ anyFS2, or CoW from anyFS2 to anyFS1.
anyFS2 (r/o) used normally.
i.e: Does the VFS provide hooks for perMount Handlers?
Thanks!
--
Al
next prev parent reply other threads:[~2006-07-09 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 17:41 Al Boldi
2006-07-08 18:32 ` Eric Van Hensbergen
2006-07-09 12:50 ` Al Boldi [this message]
2006-07-11 19:57 ` Al Boldi
2006-08-23 17:24 ` Jörn Engel
2006-08-23 18:05 ` Josef Sipek
2006-08-26 19:05 ` Al Boldi
2006-08-27 17:15 ` Jörn Engel
2006-08-28 2:10 ` Josef Sipek
2006-07-09 2:53 ` Shaya Potter
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=200607091550.36407.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome