From: Anders Henke <anders@schlund.de>
To: linux-lvm@sistina.com
Subject: [linux-lvm] rw-snapshot as an addition for lvm
Date: Sat, 28 Jul 2001 18:27:41 +0200 [thread overview]
Message-ID: <20010728182741.S13121@schlund.de> (raw)
Hi,
Currently, you take a snapshot from a logical volume and define a bufferlimit
after which the snapshot becomes invalid. As long as this limit has not
been reached, the snapshot is mountable as a readonly device.
Since journaled filesystems see a unclean fs, they do want to replay
their journal - which currently fails if the fs has not been prepared for
exactly this case where their unclean fs resides on a readonly-volume.
I think it's also quite interesting to have a rw-snapshot in which changes
of both real and snapshot are being written to a smaller bufferspace on disk:
the snapshot always represents the state of the LV when taking the snapshot,
but permits changes on 'its copy'.
However, if you're changing data on snapshot or original lv, this bufferspace
has to be used to keep the snapshot 'old' (to the time of snapshotting the lv)
as well as current (when you're writing to your snapshot). When the bufferspace
fills up, the snapshot has to return a 'disk full'-error at some point and
finally becomes invalid when too much data has been altered.
With such a function you might
-replay a journaled fs without changes for the journaled fs.
So if I want to use a snapshot for backup, I don't have to
take down the fs before snapshotting it or applying patches
to a kernel release you don't yet prefer on your systems.
-put a snapshotted database back online and perform e.g. perform
additional integrity checks (if the system really came down clean before
the snapshot has been performed or you've just a bad timing) before doing
a tape backup of the snapshots files.
-doing 'critical' or development work on a testbed without altering the
original system, e.g. test if e2fsck will unlink your critical files or
you'd better try to copy them from the unclean fs.
Or just to learn 'how can I manually try to recover this system in case
the vendor-supplied check fails'.
What do you think about such a system?
Anders
--
Schlund + Partner AG System Administration and Security
Erbprinzenstrasse 4-12 v://49.721.91374.50
D-76133 Karlsruhe f://49.721.91374.212
next reply other threads:[~2001-07-28 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 16:27 Anders Henke [this message]
2001-07-30 9:57 ` [linux-lvm] rw-snapshot as an addition for lvm Joe Thornber
2001-07-30 9:28 ` Jos Visser
2001-07-30 10:46 ` Joe Thornber
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=20010728182741.S13121@schlund.de \
--to=anders@schlund.de \
--cc=linux-lvm@sistina.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.