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

Re: [Xen-users] Hot Copy file based VMs


  • To: Javier Guerra <javier@xxxxxxxxxxx>
  • From: Jan Kalcic <jandot@xxxxxxxxxxxxxx>
  • Date: Thu, 19 Mar 2009 16:20:57 +0100
  • Cc: Jan Kalcic <jandot@xxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 19 Mar 2009 08:21:43 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=VCFinfizommWBtbbSbhDmTEf5Pl/eGj1uC4z/kTKRhXqFrmj4O0pE/b6yCIClTHldu Ra71TexlA73ZGUv01Wy9uj9N0sQfcSvL3u2fEErEUTnQgyFcfFvYdUgXUI/owTMwviP9 SSTs7FOpl92L9DVrJmF783YfxoDwYLpxXELDc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Javier Guerra wrote:
On Wed, Mar 18, 2009 at 10:46 AM, Jan Kalcic <jandot@xxxxxxxxxxxxxx> wrote:
What do you mean with "atomic" copy?


when talking about storage (or data access in general), an operation
is 'atomic' from some point of view if it's 'indivisible'. that is,
there wasn't any point in time when it was 'halfway done'.

LVM snapshots manage this, because it's not a real copy (it's more
like a fork, but it works like a copy in most cases), and because it
taps the main stream of storage operations.

most other kinds of copy can't be really atomic, that's why Fajar
tells you to suspend the guest while you do the copy.  that way, even
if there was a time when the copy was half-done, the guest wasn't
really there, so from it's point of view, the copy was atomic.


I see. Really  thanks,
Jan

_______________________________________________
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®.