From: Heinz Mauelshagen <heinzm@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] question about extending snapshots
Date: Mon, 07 Jan 2013 14:27:15 +0100 [thread overview]
Message-ID: <50EACD33.8040505@redhat.com> (raw)
In-Reply-To: <CAN4=B2mcZiiW=ErH=iNwLbQv=tWnR4bfcMG=1Tu_hvQ+b6heRQ@mail.gmail.com>
On 01/05/2013 01:00 AM, Brian Chrisman wrote:
> I'm running rhel6.2 nearly stock.
> When I mount a snapshot (writable) and perform an lvextend, the CoW
> table increases in size, but the logical volume size (for example,
> blockdev output) doesn't change itself.
You deploy more COW space to allow for a larger change set either
applied to the origin or the snapshot or both doing so, yes.
_But_ snapshots always have origin size.
> Is this impossible because the regions of the snapshot volume wouldn't
> have any corresponding regions in the origin volume?
Yes.
> Is there any way to change the size reported by a snapshot?
>
> What I'm trying to do is take a snapshot, mount it, do stuff to it,
> and if I need, make it bigger, and if I need to, just drop it and
> create a new one.
> If I just take a snapshot and modify the origin and use a merge, then
> space becomes an issue.
Watch new snapshots and thin provisioning, which'll help the space issue
in future RHEL and existjng upstream dm/lvm releases.
Heinz
>
> thanks,
> Brian
>
> _______________________________________________
> 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/
prev parent reply other threads:[~2013-01-07 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 0:00 [linux-lvm] question about extending snapshots Brian Chrisman
2013-01-07 13:27 ` Heinz Mauelshagen [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=50EACD33.8040505@redhat.com \
--to=heinzm@redhat.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).