From: Charles Marcus <CMarcus@Media-Brokers.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Temporary shapshots
Date: Mon, 05 May 2008 10:45:21 -0400 [thread overview]
Message-ID: <481F1D81.2010503@Media-Brokers.com> (raw)
In-Reply-To: <1c748a490805050730w3c303bf4y77c624ab0669641a@mail.gmail.com>
On 5/5/2008 10:30 AM, Larry Dickson wrote:
>>> To use temporary storage for snapshot, a special command for lvm
>>> would be more appropriate --- a command that would setup snapshot
>>> and write nothing about it to metadata, so that the snapshot would
>>> be forgotten on next reboot --- then, you can setup the snapshot on
>>> any device outside the volume group. You can already do this with
>>> dmsetup.
>> This is an excellent idea - and not just for ramdisks. The hardest
>> part of using snapshots for backups is making sure they are deleted
>> afterward. Not having to check at reboot would be one less 'i' to
>> dot.
> I love this idea because it nicely covers one of the main purposes of
> snapshotting, namely, making backups at a well-defined time point.
> Would there ever be any use of a temporary read-write snapshot? If
> not, perhaps making it read-only would simplify the design.
Ditto...
I feel much better now about using snapshots after realizing the OP's
problem was due to the use of a RAMdisk for a snapshot volume (combined
with an unclean shutdown), but anything that makes these safer and
easier gets my vite...
--
Best regards,
Charles
prev parent reply other threads:[~2008-05-05 14:45 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 0:53 [linux-lvm] F7 will not boot after running backup w/snapshot Gerry Reno
2008-04-30 2:29 ` Gerry Reno
2008-04-30 3:51 ` Gerry Reno
2008-04-30 14:00 ` Gerry Reno
2008-04-30 15:09 ` Larry Dickson
2008-04-30 17:23 ` Gerry Reno
2008-04-30 18:19 ` Gerry Reno
2008-04-30 18:28 ` Charles Marcus
2008-04-30 20:24 ` Gerry Reno
2008-04-30 21:19 ` Milan Broz
2008-04-30 22:30 ` Gerry Reno
2008-05-01 15:48 ` malahal
2008-05-01 16:30 ` Mikulas Patocka
2008-05-01 18:15 ` Gerry Reno
2008-05-01 18:38 ` Charles Marcus
2008-05-01 19:37 ` Gerry Reno
2008-05-01 19:42 ` Charles Marcus
2008-05-01 19:53 ` Gerry Reno
2008-05-01 20:03 ` Charles Marcus
2008-05-01 20:21 ` Gerry Reno
2008-05-01 20:25 ` Alasdair G Kergon
2008-05-01 20:30 ` Gerry Reno
2008-05-01 20:34 ` Charles Marcus
2008-05-01 20:36 ` Gerry Reno
2008-05-01 20:44 ` Charles Marcus
2008-05-01 20:57 ` Gerry Reno
2008-05-01 21:59 ` Alasdair G Kergon
2008-05-01 22:12 ` Gerry Reno
2008-05-01 23:50 ` Gerry Reno
2008-05-02 0:38 ` Stuart D. Gathman
2008-05-02 0:47 ` Stuart D. Gathman
2008-05-02 2:03 ` Gerry Reno
2008-05-02 8:14 ` Marek Podmaka
2008-05-02 14:00 ` Gerry Reno
2008-05-02 14:14 ` Charles Marcus
2008-05-02 14:25 ` Larry Dickson
2008-05-02 14:45 ` Marek Podmaka
2008-05-02 14:38 ` Stuart D. Gathman
2008-05-02 14:47 ` Bryn M. Reeves
2008-05-02 15:05 ` Marek Podmaka
2008-05-02 15:17 ` Stuart D. Gathman
2008-05-02 15:30 ` Gerry Reno
2008-05-02 15:36 ` Bryn M. Reeves
2008-05-03 2:27 ` Mikulas Patocka
2008-05-04 0:45 ` [linux-lvm] Temporary shapshots Stuart D. Gathman
2008-05-05 14:30 ` Larry Dickson
2008-05-05 14:45 ` Charles Marcus [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=481F1D81.2010503@Media-Brokers.com \
--to=cmarcus@media-brokers.com \
--cc=linux-lvm@redhat.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.