All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: tgh <tianguanhua@ncic.ac.cn>
Cc: andy@cs.ubc.ca, nikola.ciprich@linuxbox.cz,
	xen-devel@lists.xensource.com,
	Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: consistent LVM snapshot of domUs from dom0
Date: Tue, 18 Dec 2007 00:22:06 +0100 (CET)	[thread overview]
Message-ID: <alpine.LRH.0.9999.0712180018440.5143@linuxbox.linuxbox.cz> (raw)
In-Reply-To: <47639AB8.1060209@ncic.ac.cn>

Hi,
I don't know anything about parallaxfs (and neither does google it seems), 
but I guess the problem will be exactly the same. If it won't give the 
domU command to put fs into consistent state, snapshot won't be 
consistent.
hopefully I'll manage to create a fix Mark proposed...
cheers
n.

  On Sat, 15 Dec 2007, tgh wrote:

> hi
> if we use the ParallaxFS to do the filesystem snapshot, does it have the 
> similar problem ,or not? could you clear me?
>
> Thanks in advance
>
>
> Mark Williamson ??:
>>> I'd like to ask a question regarding LVM snapshots:
>>> normally if You make a snapshot of mounted LVM partition, DM
>>> infrastructure handles putting fs into consistent state using VFS
>>> infrastructure. BUT, does it work even if I make snapshot of LV used by
>>> XEN?
>>> 
>> 
>> If your LVM is running in dom0 and you snapshot the storage used by a domU 
>> then, no, it won't snapshot the domU's filesystem automatically.
>>
>> 
>>> If not, I guess it should not be that hard to fix, I guess we just need to
>>> notify domU kernel to call needed VFS function to put fs into consistent
>>> state prior to creating snapshot.
>>> 
>> 
>> Yep.
>>
>> 
>>> Can somebody comment on it, eventually correct me if I'm wrong?
>>> 
>> 
>> You're quite right.  I've just had a look at it and it looks quite feasible 
>> to do this.  The obvious simple way to implement it would be to add an xm 
>> command that causes a domain to freeze its filesystems into a consistent 
>> state and then return when that is done.
>> 
>> e.g.
>> 
>> xm create mydomain
>> xm fs_freeze mydomain
>> <do backup>
>> xm fs_unfreeze mydomain
>> 
>> Ideally the backup operation would just take a snapshot e.g. using LVM or 
>> qcow.  With a bit more tools / storage integration we could have an "xm 
>> safesnapshot" command that would create a coherent snapshot of the disk.
>> 
>> It would be awesome.
>> 
>> Cheers,
>> Mark
>>
>> 
>
>
>

-- 

  reply	other threads:[~2007-12-17 23:22 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
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 [this message]
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.0712180018440.5143@linuxbox.linuxbox.cz \
    --to=extmaillist@linuxbox.cz \
    --cc=andy@cs.ubc.ca \
    --cc=mark.williamson@cl.cam.ac.uk \
    --cc=nikola.ciprich@linuxbox.cz \
    --cc=tianguanhua@ncic.ac.cn \
    --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.