From: Tony Asleson <tasleson@redhat.com>
To: lvm-devel@redhat.com
Subject: master - python-lvm: Make second lv.snapshot() argument optional
Date: Mon, 17 Dec 2012 08:51:37 -0600 [thread overview]
Message-ID: <50CF3179.8090406@redhat.com> (raw)
In-Reply-To: <50CCECF7.8000809@redhat.com>
On 12/15/2012 03:34 PM, Zdenek Kabelac wrote:
> 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)
How does a user calculate the correct size?
I would like to see an option to pass on snapshot creation that can
safely create a snapshot where every block can get written.
Regards,
Tony
prev parent reply other threads:[~2012-12-17 14:51 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
2012-12-16 2:27 ` Andy Grover
2012-12-16 18:58 ` Zdenek Kabelac
2012-12-17 14:51 ` Tony Asleson [this message]
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=50CF3179.8090406@redhat.com \
--to=tasleson@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.