All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Marxmeier <mike@msede.com>
To: Jay Weber <jay@lazy.accessus.net>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] Snapshot documentation
Date: Wed, 08 Mar 2000 04:00:15 +0100	[thread overview]
Message-ID: <38C5C23F.10C2F1AF@msede.com> (raw)
In-Reply-To: Pine.OSF.4.21.0003071740130.28917-100000@lazy.accessus.net

Jay Weber wrote:
> Been playing with snapshots and am noticing I can create a snapshot with
> less PE's than my source LV that I'm snapshotting, with the small side
> effect of:
> 
> lvcreate -- WARNING: all snapshots will be disabled if more than 12 MB are
> changed

For now snapshots use a COW model at the block level. Each modified 
block gets saved (once) to the snapshot area. If the space dedicated 
to the snapshot area is exhausted the snapshot is discarded (and the
the saved blocks are simply discarded). Otherwise the fs would become
inconsistent.

When/if LVM once has persistent snapshots this might need to change.

> Is the above message implying that if I change more than 12MB of data on
> my source LV that the snapshot is then defunct/useless?  Does that include
> deletes, etc?

Yes. Though deletes should only affect the inode and lists of indirect
blocks (if any) so deleting a 12MB files does not necessarily result 
in 12MB of changes.


Hope this helps
Michael

-- 
Michael Marxmeier           Marxmeier Software AG
E-Mail: mike@msede.com      Besenbruchstrasse 9
Phone : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420     http://www.msede.com/

  reply	other threads:[~2000-03-08  3:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-07 23:46 [linux-lvm] Snapshot documentation Jay Weber
2000-03-08  3:00 ` Michael Marxmeier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-08  8:12 Heinz Mauelshagen

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=38C5C23F.10C2F1AF@msede.com \
    --to=mike@msede.com \
    --cc=jay@lazy.accessus.net \
    --cc=linux-lvm@msede.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.