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

Re: [linux-lvm] LVM multiple Snpshots implementation query



Thanks a lot.
I wasnt of the patch.

Yes, I am looking for a similar thing.
Right now after snapshot the cow is done for all the snapshots if there is a write on origin.

This is an obvious thing. Wondering it was missed in original lvm/dm snapshot code.

Any idea?


--- On Tue, 11/5/10, Busby.Cheung <chaimvy 163 com> wrote:

From: Busby.Cheung <chaimvy 163 com>
Subject: Re: [linux-lvm] LVM multiple Snpshots implementation query
To: "LVM general discussion and development" <linux-lvm redhat com>
Date: Tuesday, 11 May, 2010, 7:44 AM

Did you mean you want to use something like shared-snapshot? COW once?
I know shared-snapshot implemented by Mikulas and others:
 


 

在2010-05-10,"andiket a" <truly_linux yahoo co in> 写道:
-----原始邮件-----
发件人:"andiket a" <truly_linux yahoo co in>
发送时间:2010年5月10日 星期一
收件人:linux-lvm redhat com
主题:[linux-lvm] LVM multiple Snpshots implementation query

Hi,

If there are multiple snapshots then write to origin is an expensive operation.
My understanding after looking at the code of orig_wirte() is that if a write comes on a chunk on orig device then cow is initiated for all the snapshots.
This is an expensive operation for sure.

Does anyone know if there was any reason behind implementing it like this?

Thanks,
Andiket.




网易为中小企业免费提供企业邮箱(自主域名)

-----Inline Attachment Follows-----

_______________________________________________
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/


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