From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Domain saving and filesystem corruption Date: Mon, 26 Jun 2006 16:13:00 -0500 Message-ID: <44A04DDC.2000600@us.ibm.com> References: <449DD996.7000501@ultraviolet.org> <8c2b0fbdd8c4018db50c9612dd11550d@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8c2b0fbdd8c4018db50c9612dd11550d@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel , Tracy R Reed List-Id: xen-devel@lists.xenproject.org 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