Re: snapshots documentation clarification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux