WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] xm save fails on OCFS2

To: "XEN Mailing List" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] xm save fails on OCFS2
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Sun, 28 Sep 2008 21:42:37 -0600
Delivery-date: Sun, 28 Sep 2008 20:43:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I'm currently running a set of SLES10 SP2 servers that share common storage using OCFS2.  The VMs run fine, although sometimes it seems that the disk files don't close out correctly and I end up with loop devices that won't detach correctly.  The bigger issue, though, is that if I try to do an "xm save" on a domain and put the file onto the OCFS2 volume, the save fails after a couple of seconds and a few bytes of data.  If I save the file to the local filesystem (ext3 or rieser) it works fine, but a save to the OCFS2 volume doesn't seem to work.  Also, once the xm save fails, the domain gets into a weird state that an "xm restore" or "xm resume" or "xm unpause" doesn't seem to help.  Then I have to reboot the physical server because the qemu-dm process goes into a "defunct" state and won't close out and release the file.  Unfortunately I didn't get log files the last time this happened, but I'll try to capture that the next time I see the behavior.  In the meantime, if anyone else has any ideas, I'd appreciate the input.
 
Thanks - Nick


This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>