linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Mike Snitzer" <snitzer@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] snapshots documentation clarification
Date: Tue, 27 Feb 2007 20:04:25 -0500	[thread overview]
Message-ID: <170fa0d20702271704w469bec42t743b33d4dd82c584@mail.gmail.com> (raw)
In-Reply-To: <4384431.130961172620690322.JavaMail.root@zimbra.greatschools.net>

On 2/27/07, Dane Miller <dane@greatschools.net> wrote:
>
> Section 3.8 "Snapshots" of the LVM Howto has a scary warning after the first paragraph (http://tldp.org/HOWTO/LVM-HOWTO/snapshotintro.html), with a caveat in the last sentence:
>   "If the snapshot size equals the origin size, it will never overflow."
>
> What exactly does this mean?

It means there isn't any risk of the snapshot LV getting invalidated
because of overflow.  Reason being, the copy-on-write would only ever
fill (but _not_ overflow) the snapshot LV if the entire origin LV
changed.  Even if that were the case you wouldn't overflow because the
snap LV would accomodate such extensive change.

That said, I can't see how a long-term (3yr) _single_ snapshot is
useful but thats up to you.  Generally snapshots are done periodically
rather than maintaining a single snap for such a long period.  Do you
understand that LVM snapshots need a new snapshot LV for each snapshot
you create?  So if you want N snapshots, without the risk of overflow,
during the 3yr period you'd consume N*(size_of_origin_LV) space.

Mike

  reply	other threads:[~2007-02-28  1:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 23:58 [linux-lvm] snapshots documentation clarification Dane Miller
2007-02-28  1:04 ` Mike Snitzer [this message]
2007-02-28  1:13 ` Dane Miller

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=170fa0d20702271704w469bec42t743b33d4dd82c584@mail.gmail.com \
    --to=snitzer@gmail.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 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).