From: Sandy Harris <pashley@storm.ca>
To: Libor Vanlk <libor@conet.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Adding snapshot capability to Linux
Date: Mon, 22 Apr 2002 14:19:07 -0400 [thread overview]
Message-ID: <3CC4541B.1999F853@storm.ca> (raw)
In-Reply-To: <3CC3ECD2.9000205@conet.cz> <20020422170745.GD3017@turbolinux.com>
Andreas Dilger wrote:
>
> On Apr 22, 2002 12:58 +0200, Libor Vanlk wrote:
> > I'm going to start my dissertation work which is "Adding snapshop
> > capability to Linux kernel with copy-on-write support". ...
> > So I'd like if you can send me any suggestions/tips/warnings/links etc.
> > before I start coding so I know what should I avoid/use.
>
> Please see:
> http://www-mddsp.enel.ucalgary.ca/People/adilger/snapfs/
>
> What you describe is exactly what snapfs does. ...
A related thing to look at would be the Plan 9 file system.
http://www.cs.bell-labs.com/plan9dist/
It is an entirely different design using copy-on-write and a
form of snapshotting such that something like:
cd //2001/12/25/foo
puts the user in directory /foo as it was at daily backup time
on Christmas day last year.
The original Plan 9 system used WORM drives with hard drives
acting as cache. I suspect the design could work without WORM.
prev parent reply other threads:[~2002-04-22 19:17 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
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 [this message]
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=3CC4541B.1999F853@storm.ca \
--to=pashley@storm.ca \
--cc=libor@conet.cz \
--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 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.