All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitsuhiro Tanino <mtanino@redhat.com>
To: lvm-devel@redhat.com
Subject: Nested logical volume snapshot on shared storage
Date: Mon, 24 Mar 2014 17:16:41 -0400	[thread overview]
Message-ID: <5330A0B9.5000105@redhat.com> (raw)

Hi

I would like to know latest activity of nested logical volume snapshot.
In my understanding, nested LV snapshot is only supported when we use LVM thin volume.
Referring the document, thin volume are not supported across the nodes in a cluster
or shared with several servers. Therefore, there is no feature to provide nested
LV snapshot across several nodes.

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/thinprovisioned_volumes.html

I think nested logical volume snapshot is very useful feature for cloud environment.
For example,
If user create a new VM from LV snapshot, the VM can boot quickly because LVM snapshot
is ablle to create rapidly and also it can save disk usage.
And if nested LV snapshot is supported, user can retrieve a VM which is created by
LV snapshot to former state after applying some configurations. Nested snapshot
is already supported by qcow2.

Following figure is shown above example.
I would appreciate if anyone let me know an activity of nested snapshot.

---------
* Mgmt node(serv01): Manage. volume creation using snapshot, volume deletion
                      snapshot creation using nested LVM snapshot, snapshot deletion
* HV node1(srv02)  : Attach a snapshot to a VM and run KVM guest.
* HV node2(srv03)  : Same as HV node1.
  
  thX: thin volume including KVM guest boot image.
  snX: snapshot from thin volume.

+---------------+  +---------------+  +---------------+
|     srv01     |  |     srv02     |  |     srv03     |
|   Mgmt node   |  |    HV node1   |  |    HV node2   |
|               |  |       +---+   |  |         +---+ |
|               |  |       |VM1|   |  |         |VM2| |
|               |  |       +-+-+   |  |         +-+-+ |
|               |  |         |     |  |             | |
+---+---+---+---+  +---+---+-+-+---+  +---+---+---+-+-+
|th1|th2|sn1|sn2|  |th1|th2|sn1|sn2|  |th1|th2|sn1|sn2|
+---------------+  +---------------+  +---------------+
|   dm-thin01   |  |   dm-thin01   |  |   dm-thin01   |
+---------------+  +---------------+  +---------------+
|     vg01      |  |     vg01      |  |     vg01      |
+---------------+  +---------------+  +---------------+
       |FC1               |FC2               |FC3
       |                  |                  |
------+------------------+--------+---------+----------
                                   |
                           +-------+--------+
                           | A Logical Unit |
                           +----------------+

-- 
Regards,
Mitsuhiro Tanino



                 reply	other threads:[~2014-03-24 21:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5330A0B9.5000105@redhat.com \
    --to=mtanino@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.