All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: master - python-lvm: Make second lv.snapshot() argument optional
Date: Sat, 15 Dec 2012 22:34:47 +0100	[thread overview]
Message-ID: <50CCECF7.8000809@redhat.com> (raw)
In-Reply-To: <20121214221108.E6D52137F@hosted02.fedoraproject.org>

Dne 14.12.2012 23:11, Andy Grover napsal(a):
> Gitweb:        http://git.fedorahosted.org/git/?p=lvm2.git;a=commitdiff;h=0958905b1bc0a59d34a4092377bae7c59f424181
> Commit:        0958905b1bc0a59d34a4092377bae7c59f424181
> Parent:        0e3093979e901384aecb22e08d83b5acb2ef12c1
> Author:        Andy Grover <agrover@redhat.com>
> AuthorDate:    Fri Dec 14 14:10:41 2012 -0800
> Committer:     Andy Grover <agrover@redhat.com>
> CommitterDate: Fri Dec 14 14:10:41 2012 -0800
>
> python-lvm: Make second lv.snapshot() argument optional
>
> If no size is given, size defaults to 0, which in lvm_lv_snapshot will
> allocate extents equal to the original LV be allocated for the new
> snapshot.
>


Possibly not the ideal solution here.

1) we have some clash with command line 'API'
    user creates snapshot of thin volume
       - without giving size he get thin volume snaphost.
         lvcreate -s
       - with size specified he gets 'old' snapshot
         (snapshot outside of the pool)
         lvcreate -s -l|-L

2) using same size of origin is not enough to cover
    i.e. full rewrite of origin device - you need some
    'extra' size to store snapshot's metadata (remapping blocks)

Zdenek



  reply	other threads:[~2012-12-15 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 22:11 master - python-lvm: Make second lv.snapshot() argument optional Andy Grover
2012-12-15 21:34 ` Zdenek Kabelac [this message]
2012-12-16  2:27   ` Andy Grover
2012-12-16 18:58     ` Zdenek Kabelac
2012-12-17 14:51   ` Tony Asleson

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=50CCECF7.8000809@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=lvm-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 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.