From: Luke S Crawford <lsc@prgmr.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: LVM Snapshot Feature
Date: 01 Aug 2008 10:15:18 -0400 [thread overview]
Message-ID: <m3sktoddop.fsf@luke.xen.prgmr.com> (raw)
In-Reply-To: <4DE0C34D8B0DA64C9585DC45C36EA03BAB0788@dewdfe1g.wdf.sap.corp>
"Bombardier, Pascal" <pascal.bombardier@sap.com> writes:
> In your opinion, does it make sense to be able to create non-persistent
> snapshots ?
> In the case of a filesystem backup, a non-persistent snapshot would be a
> snapshot that we agree to lose in case of failure or reboot. If anything
> happens, a server administrator would have to recreate a new snapshot
> and then restart the backup.
Considering the current failure mode when a snapshot becomes 'full' (that
is, when I run out of space to remap changed blocks the snapshot becomes
corrupted) this is the only way I currently feel comfortable using LVM
snapshots at all, so personally, I think snapshots that did not persist
through reboots would be quite useful.
next prev parent reply other threads:[~2008-08-01 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 7:35 LVM Snapshot Feature Bombardier, Pascal
2008-08-01 14:15 ` Luke S Crawford [this message]
2008-08-01 15:52 ` Adam Hamsik
2008-08-04 13:15 ` Mikulas Patocka
2008-08-06 6:08 ` haad
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=m3sktoddop.fsf@luke.xen.prgmr.com \
--to=lsc@prgmr.com \
--cc=dm-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox