From: "Harald Heigl" <Harald_Heigl@gmx.at>
To: linux-lvm@redhat.com
Subject: [linux-lvm] What happens with full snapshots
Date: Fri, 12 Feb 2010 15:56:11 +0100 [thread overview]
Message-ID: <001501caabf3$85080b60$8f182220$@at> (raw)
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Hello,
I'm relatively new to lvm, I'm using Fedora for almost 3 years, but up to
now I just set up lvm on install, formatted my ext3/ext4 and it just works.
Now I want to go somehow deeper playing around with snapshots.
I know you should size your snapshot volume to a size that can hold all the
changes. As I see a snap lv only contains the "original" datachunks and the
original lv is in a normal state as if there were no snapshot.
My questions:
1. What happens if the snap gets full (e.g. someone copies large data
from one lv to a snapshotted lv or something other you didn't expect), some
sites say it original and snapshot gets deactivated, some sites say the snap
lv gets invalidated. What does this mean? Is my original volume just crap
afterwards or can I work on as usual (with the difference that nothing is
written on the snap anymore), or just need to remove the snap ..
2. What happens if there is a problem with a snap? I've heard on
reboot the snapshots are lost. What if there is a power shortage, so the
snap is lost, you boot and the original lv just seeks for the snap? Are
there implications on this. Can you just mount such a original lv or do you
have to remove the (non existent) snap lv before (How can you remove a
snapshot that doesn't exist anymore)
That would be nice to know before I use snaps.
Thanks in advance,
Harald (Harry) Heigl
[-- Attachment #2: Type: text/html, Size: 4932 bytes --]
next reply other threads:[~2010-02-12 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 14:56 Harald Heigl [this message]
2010-02-12 15:37 ` [linux-lvm] What happens with full snapshots Ray Morris
2010-02-12 16:41 ` Harald Heigl
2010-02-12 19:22 ` Ray Morris
2010-02-13 7:13 ` Harald Heigl
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='001501caabf3$85080b60$8f182220$@at' \
--to=harald_heigl@gmx.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).