All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: andy@cs.ubc.ca, nikola.ciprich@linuxbox.cz,
	xen-devel@lists.xensource.com
Subject: Re: consistent LVM snapshot of domUs from dom0
Date: Fri, 4 Jan 2008 10:32:28 +0100 (CET)	[thread overview]
Message-ID: <alpine.LRH.0.9999.0801041030430.5855@linuxbox.linuxbox.cz> (raw)
In-Reply-To: <200712241639.17100.mark.williamson@cl.cam.ac.uk>

On Mon, 24 Dec 2007, Mark Williamson wrote:
Hi Mark,
is there some progress regarding this subject? Still, if there is 
something I could help with, please do not hesitate to tell me what could 
I do...
Cheers
Nik

>
> Yes, I think that's a sensible first step to take.  Later on, we could perhaps
> look into putting some more smarts in, e.g. doing the snapshot creation
> automatically in the case that an LVM volume or QCow virtual disk is already
> being used.
>
> I hadn't come across freeze/thaw_bdev before - I'd found a lock / unlock call
> for filesystem locking somewhere that looked promising but not implemented it
> yet.  I imagine it might boil down to a similar thing in the end.
>
> Either way, being able to freeze specific block devices could be useful for
> backup purposes.  There's no point freezing filesystems that are not used to
> store backed-up data, for instance!
>
>>
>> Yup, agree :)
>> Cheers!
>
> OK, I'll try and get some code online at some point and let you know when it's
> available.

  reply	other threads:[~2008-01-04  9:32 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
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 [this message]
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.0801041030430.5855@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=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.