From: Jasper Spaans <jasper@spaans.ds9a.nl>
To: Libor Vanek <lists@conet.cz>
Cc: "Peter Wächtler" <pwaechtler@loewe-komp.de>,
linux-kernel@vger.kernel.org
Subject: Re: Adding snapshot capability to Linux
Date: Mon, 22 Apr 2002 14:42:44 +0200 [thread overview]
Message-ID: <20020422124244.GA18252@spaans.ds9a.nl> (raw)
In-Reply-To: <3CC3ECD2.9000205@conet.cz> <3CC3FCD2.2030008@loewe-komp.de> <3CC3FFC8.8020309@conet.cz>
On Mon, Apr 22, 2002 at 02:19:20PM +0200, Libor Vanek wrote:
> > > I'm going to start my dissertation work which is "Adding snapshop
> > > capability to Linux kernel with copy-on-write support". My idea is
> > > add it as another VFS - I know that there is some snapshot support in
> > > LVM but it's working on "device-level" and I'd like/have to do it on
> > > fs level.
>
> But AFAIK it doesn't work on fs level but (i.e. you cannot make snapshot
> of some directory which contains NFS/Samba mapped dirs).
I'm sorry to have to say this, but making snapshots of remote filesystems is
kinda silly and impossible - if you implement it at the FS level.
To make a snapshot, you will have to be able to transfer the whole state of
the (remote) filesystem atomically (atomically on the remote server) which
will not happen when you don't have support for such functionality on that
server (think of other clients writing to that FS). Besides that, think of
the possible amounts of memory needed to store this snapshot locally, and
you should come to the conclusion that implementing snapshots at the FS
level is hairy, if not impossible.
You could however try to set up a snapshotting-system outside of LVM, though
that could become tricky too since LVM provides a nice way of reserving
space to store changes on the snapshotted fs. (To get back to your
original idea, you could implement a system like this and add some server
scripts to it, so a client can create and see a snapshotted version)
Regards,
--
Jasper Spaans
http://jsp.ds9a.nl/contact/
Tel/Fax: +31-84-8749842
next prev parent reply other threads:[~2002-04-22 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 10:58 Adding snapshot capability to Linux Libor Vaněk
2002-04-22 12:06 ` Peter Wächtler
2002-04-22 12:19 ` Libor Vanek
2002-04-22 12:42 ` Jasper Spaans [this message]
2002-04-22 15:02 ` Alvaro Figueroa
2002-04-23 5:36 ` rpm
2002-04-23 14:30 ` Alvaro Figueroa
2002-04-23 14:45 ` Alexander Viro
2002-04-23 14:58 ` Xavier Bestel
2002-04-23 18:48 ` Libor Vanek
2002-04-23 19:04 ` Jeremy Jackson
2002-04-23 20:22 ` Andreas Dilger
2002-04-22 17:07 ` Andreas Dilger
2002-04-22 17:41 ` Kent Borg
2002-04-22 18:39 ` Andreas Dilger
2002-04-22 18:19 ` Sandy Harris
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=20020422124244.GA18252@spaans.ds9a.nl \
--to=jasper@spaans.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@conet.cz \
--cc=pwaechtler@loewe-komp.de \
/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