qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC] qemu snapshot enchancement


From: Wenchao Xia
Subject: Re: [Qemu-devel] [RFC] qemu snapshot enchancement
Date: Fri, 25 Jan 2013 10:01:04 +0800
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2

于 2013-1-24 13:51, Dietmar Maurer 写道:
   * Like Case 2, the benefit isn't clear to me.  In a scenario where you
     use both QEMU and LVM snapshots there is now an extra management
     overhead of cleaning up 2 snapshots instead of just 1 when the user
     wants to delete a snapshot.  I think this will be a headache.

    My understanding is internal snapshots is obvious fast in both deleting and
reading, and I have similar questions, Dietmar, could u tip more how you use
this case while 2 snapshot layer exist?

To be honest, I don't really understand what you talk about here. There are 
simply
different storage types and file formats. There are several storage types with
support for internal snapshots:

* traditional qcow2 files on normal file system
* newer file systems (zfs, btrfs)
* lvm (new dm-thin pools)
* RDB (ceph)
* sheepdog
* iSCSI and nexenta API
*...

And you simply want to allow an external library to create/remove the snapshot 
for you.



  I remember you have a patch enable take qcow2 internal snapshot for
every block device, and then will you use LVM to take another LVM
snapshot for it? If not how did you treat this qcow2 internal snapshot
later?



--
Best Regards

Wenchao Xia




reply via email to

[Prev in Thread] Current Thread [Next in Thread]