From: Anthony Liguori <aliguori@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Tracy R Reed <treed@ultraviolet.org>
Subject: Re: Domain saving and filesystem corruption
Date: Mon, 26 Jun 2006 16:13:00 -0500 [thread overview]
Message-ID: <44A04DDC.2000600@us.ibm.com> (raw)
In-Reply-To: <8c2b0fbdd8c4018db50c9612dd11550d@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 25 Jun 2006, at 01:32, Tracy R Reed wrote:
>
>> I mentioned this to someone on the IRC channel and they said "That is
>> documented behavior." Unfortunately that doesn't bring back my data. It
>> wasn't documented when I started using Xen and I can't possibly keep up
>> on everything written about Xen in the meantime.
>
> I'm not sure if the behaviour is documented, but it certainly isn't
> new. Save/restore has always behaved like that -- a filesystem should
> be considered 'locked down' by a guest except when the guest OS is
> shut down cleanly. No interlock is enforced or metadata maintained for
> this in open source tools.
You really ought to avoid save/restore/migrate when not using network or
checkpointable storage. You will almost certainly eventually get some
sort of corruption.
I didn't realize xend actually tries to save domains on shutdown. Seems
like a bad idea to me. Is this correct? Is this only for domains
started with /etc/init.d/xendomains?
Regards,
Anthony Liguori
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-06-26 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 0:32 Domain saving and filesystem corruption Tracy R Reed
2006-06-26 20:59 ` Keir Fraser
2006-06-26 21:13 ` Anthony Liguori [this message]
2006-06-26 22:05 ` Tracy R Reed
2006-06-27 2:45 ` Eric Peterson
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=44A04DDC.2000600@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=treed@ultraviolet.org \
--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.