All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Stefan de Konink <skinkie@xs4all.nl>
Cc: nikola.ciprich@linuxbox.cz, xen-devel@lists.xensource.com,
	Mark Williamson <mark.williamson@cl.cam.ac.uk>,
	Mike Sun <msun@gatech.edu>
Subject: Re: consistent LVM snapshot of domUs from dom0
Date: Sat, 8 Dec 2007 23:17:11 +0100 (CET)	[thread overview]
Message-ID: <alpine.LRH.0.9999.0712082300510.14596@linuxbox.linuxbox.cz> (raw)
In-Reply-To: <475B1148.30301@xs4all.nl>

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

-- 

  reply	other threads:[~2007-12-08 22:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07  7:34 consistent LVM snapshot of domUs from dom0 Nikola Ciprich
2007-12-08 18:26 ` Mark Williamson
2007-12-08 21:01   ` Mike Sun
2007-12-08 21:39     ` Nikola Ciprich
2007-12-08 21:48       ` Stefan de Konink
2007-12-08 22:17         ` Nikola Ciprich [this message]
2007-12-08 22:25           ` Mike Sun
2007-12-08 23:23             ` Mark Williamson
2007-12-08 23:16         ` Mark Williamson
2007-12-08 23:03     ` Mark Williamson
2007-12-08 21:37   ` Nikola Ciprich
2007-12-08 22:59     ` Mark Williamson
2007-12-15  9:13   ` tgh
2007-12-17 23:22     ` Nikola Ciprich
2007-12-19 18:53       ` Mark Williamson
2007-12-24 15:22         ` Nikola Ciprich
2007-12-24 16:39           ` Mark Williamson
2008-01-04  9:32             ` Nikola Ciprich
2008-01-04 14:32               ` Mark Williamson
2008-01-04 16:50               ` Mark Williamson
2008-01-04 22:42                 ` Nikola Ciprich
2008-01-05  2:54                   ` Mark Williamson
2008-01-05 11:07                     ` Nikola Ciprich
2008-01-07  2:25                       ` Mark Williamson
  -- strict thread matches above, loose matches on Subject: below --
2007-12-06 15:48 Nikola Ciprich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.0.9999.0712082300510.14596@linuxbox.linuxbox.cz \
    --to=extmaillist@linuxbox.cz \
    --cc=mark.williamson@cl.cam.ac.uk \
    --cc=msun@gatech.edu \
    --cc=nikola.ciprich@linuxbox.cz \
    --cc=skinkie@xs4all.nl \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.