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

Re: [Xen-users] Xen 4.0 feature request

  • To: Nathan Eisenberg <nathan@xxxxxxxxxxxxxxxx>
  • From: Jan Kalcic <jandot@xxxxxxxxxxxxxx>
  • Date: Tue, 07 Jul 2009 23:42:39 +0200
  • Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 07 Jul 2009 14:40:00 -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=J6p9tgsxyYkUleeRevyduyTFZonQgM/B33Emup3IbyJk0uf1SlbX077km/O+HmcZC5 1Kz4VYTP0DU8bLy0riPMGOdqy7qttQpY8iUR0RR2A5+sIf78Pm8BIllLKRqUcgYjS5gR t5veVA3VenqkFgrmJ0DGTUUDY58E34Mjj1jNo=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Nathan Eisenberg wrote:
> The fact of the matter is that without flushing the buffers and cache, the 
> snapshot is essentially the same as what would result if you pulled the power 
> plug (sans the messy 'memory death' results that happen in the physical world 
> in the nanoseconds after RAM loses power) -and while that's hardly ideal, 
> it's good enough for many purposes - databases and filesystems  are generally 
> robust enough to handle uncommitted transactions.
> However, there are ways to get a better snapshot.  All you need is a quick 
> script that logs in to the domU,  stops the database service, runs a sync, 
> and then generates the snapshot and starts the database service again.
Doesn't  a xm pause work it out?

> Best Regards
> Nathan Eisenberg
> Sr. Systems Administrator
> Atlas Networks, LLC
> support@xxxxxxxxxxxxxxxx
> http://support.atlasnetworks.us/portal
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Simon Hobson
> Sent: Monday, July 06, 2009 11:26 AM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Xen 4.0 feature request
> Nathan Eisenberg wrote:
>> Why can't you save only one VM with LVM snapshots?  Sounds like you 
>> have an odd implementation, rather that there being a problem with 
>> LVM.  We export two LVs per domU - 1 'data' and 1 'swap'.  I can 
>> easily snapshot the 'data' LV of any single domU without a 
>> performance problem.
> How do you deal with the fact that you are snapshotting a dirty state 
> ? Unless you are using LVM inside the DomU (in which case Xen is 
> irrelevant), then when you make a snapshot, it will NOT include any 
> dirty blocks in the guests cache.
> Unless you collaborate with the guest, get it to stop updating the 
> filesystem, and flush it's cache - then you are pretty well 
> guaranteed dirty (and probably corrupt) data.

Xen-users mailing list



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