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

[Xen-users] COW (Copy-On-Write) storage options in Xen


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Mark Ryden" <markryde@xxxxxxxxx>
  • Date: Sat, 3 Mar 2007 09:16:04 +0200
  • Delivery-date: Fri, 02 Mar 2007 23:15:20 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Cbm+1a+zkFjtsQhs4vZ2Ta22Kb9UW+CU0cA5BKt+MQVleLxLSkobXzNKExVmwAhZ4lNnv7SjrZJGGYL0UIQgnncGuohSP6q2BRcDEL4LnsbRRav98SFZ1FBy8jtrMPHiKN/c/pMqoA01y9mnMJLgcAqYSw2vQK6R/kPD/BLwLBA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

Does anybody have an experience (good or bad) with using
COW (Copy-On-Write) storage in Xen ?

I saw that there is a (rather small) wiki page about it :
http://wiki.xensource.com/xenwiki/COWHowTo

And also some instructions from Michael Lang for using
unionfs for COW for Xen:
http://wiki.xensource.com/xenwiki/InstructionsFromMichaelLang

My question is :
There are some altenatives which are discussed in that wiki page:
unionfs, blktap ,using qemu: see
http://lxr.xensource.com/lxr/source/tools/blktap/,
BenRin's Copy-on-Write md device,Translucency , DmUserspace
,parallax, CowNFS , and LVM snapshots (According to MichaelVrable wiki
as I understood it).

What are the pros and cons of these options ? is there a  preferred
one when using Xen ?

Regards,
Mark Ryden

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.