From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikola Ciprich Subject: Re: consistent LVM snapshot of domUs from dom0 Date: Sat, 8 Dec 2007 23:17:11 +0100 (CET) Message-ID: References: <200712081826.23257.mark.williamson@cl.cam.ac.uk> <475B1148.30301@xs4all.nl> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Return-path: In-Reply-To: <475B1148.30301@xs4all.nl> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan de Konink Cc: nikola.ciprich@linuxbox.cz, xen-devel@lists.xensource.com, Mark Williamson , Mike Sun List-Id: xen-devel@lists.xenproject.org Hi Mike, well, I maybe don't understand where the question is ;) but I guess that Your procedure is perfectly correct (for creation of a checkpoint of running system), if You want to restore the backup later, You restore system into running state, so a filesystem is in state consistent with running system.... n. On Sat, 8 Dec 2007, Stefan de Konink wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Nikola Ciprich schreef: >> Hi Mike, >> I think that this problem can be solved using procedure Mark proposed - >> freeze filesystems of all running domUs using some xm command, then >> create snapshot and unfreeze them all again. I think that You won't need >> suspend at all. >> We just now need to implement it :) > > > Just a question about unsafely. I have implemented iscsi and zfs as > combination with Xen on Linux. Is the only safe procedure: > > pause memory snapsnot > [send out disk snapshot] > resume > > > Stefan > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHWxFIYH1+F2Rqwn0RCiT7AKCBAnfW4E0M8pLjHKZUHOOX0mwoZwCfcfY3 > Rns2S2AETOMypqLDmRnljx4= > =ADlt > -----END PGP SIGNATURE----- > > --