From: David Masover <ninja@slaphack.com>
To: Paul Wagland <paul@kungfoocoder.org>
Cc: reiserfs-list@namesys.com, tdwebste2@yahoo.com,
Vladimir Saveliev <vs@namesys.com>,
Markus TXrnqvist <mjt@nysv.org>,
Valdis.Kletnieks@vt.edu
Subject: Re: snapshot, checkpoints
Date: Wed, 09 Jun 2004 17:21:58 -0500 [thread overview]
Message-ID: <40C78D86.2060305@slaphack.com> (raw)
In-Reply-To: <116CD3CA-B709-11D8-A933-000A95CD704C@kungfoocoder.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paul Wagland wrote:
| At least with LVM, and therefore I assume with device mapper, the
| "snapshot" only stores changed blocks. From what I understand, this
| means that when you take a snapshot, if you change a block in the
| original, it first copies it to the snapshot, and then writes the new
| block to the original system. Of course, you will run into a problem if
| more changes are made than the snapshot partition size, but AFAIK it
| then just disables the snapshot.
Good, then we don't have to immediately rewrite the wheel. But I still
would rather that we do this eventually. My concept has the changes
stored on the same partition, seems like it may be faster, and opens the
door for a filesystem-based cvs.
Think about that! I mean, if copy-on-capture is what I think it is,
then things like 'cp' could be extended to copy using a system call
(similar to how 'ln' works). Probably a few utilities would have to be
extended, but the net result is, you don't have to say you're doing
something in a cvs dir for it to be cosidered a cvs action (just do 'cp'
instead of 'cvs cp' or whatever). You don't "check out" different
versions, you just look in different folders.
(I'm using 'cvs' in the generic sense -- could work as easily for
bittorrent or anything else.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQMeNhngHNmZLgCUhAQLe6w/+I5Emoxp6pLDA+9Ncd7UK0ZSkQsT0lwqu
jofkphMJ6hKZhE4KSB5IYup7Xh2ZqUZu1v+9gj0d/tLHatpCfLLklZJn0gKRA9+f
wUBY5VD18VmuWO0Zhi1R7QGAzijCThvyJTmhlu56E6dXEaQTxu7OufLmwfGDFgeT
LN3I/diPXVPp4AihzeFqT7F3/cYQgK/6wYgx9kB8QWsq9qcRzXY1XghuPgyoWJ9Y
AtIFmHmKLu9vP2S0mh7u6sv9R1UlzwdKZhpdxESytMqOV1m1xQbLdi5wLkS37i9l
Y9oxuhXXjiK+bkEwwdr+7/Ide1CzaRDthlBUMT+jy+zKekQLRLJtiZi3IhZeRb6V
UbO5SmHUqTxBltMEmp5zDMTX7QtT+n663GQCBzepMX55u9VWGTKrGYuSxDeJF5T7
5BT+FZ/UtY9ONL3hFFzMwAtaiI4r7rEIx0t2R1TVhsUhV69KmUXs4A2I0WOXPG4i
wFIQAjyX6BQtP3nn1QKIfeqpTRSHO2wPBC8dEAL8fFiiEBh/HEQdbbWCVCD3hj7G
0iNoLvL6w3qfPG+rRZtRdIn0apyd4zus0vWNpWWT8jh/QUeHGp97kzoEP3MQUlYk
kyVdFgwiX63l1AtJh6MWTDA2iVvegiaCY9Uuna5H77yJkV7uw8vc+TfRGRiq2otU
N7AQvJK8OBU=
=Nr9u
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-09 22:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 6:52 snapshot, checkpoints Timothy Webster
2004-05-27 7:03 ` Vladimir Saveliev
2004-05-27 9:27 ` mjt
2004-05-27 10:40 ` Heinz-Josef Claes
2004-06-04 11:10 ` Paul Wagland
2004-06-04 19:25 ` Valdis.Kletnieks
2004-06-05 4:39 ` David Masover
2004-06-05 15:57 ` Paul Wagland
2004-06-09 22:21 ` David Masover [this message]
2004-06-10 4:54 ` Pierre Etchemaite
2004-06-10 5:20 ` Hans Reiser
2004-06-10 22:15 ` David Masover
2004-06-11 2:27 ` Hans Reiser
2004-06-11 21:04 ` David Masover
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=40C78D86.2060305@slaphack.com \
--to=ninja@slaphack.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=mjt@nysv.org \
--cc=paul@kungfoocoder.org \
--cc=reiserfs-list@namesys.com \
--cc=tdwebste2@yahoo.com \
--cc=vs@namesys.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.