Re: [Xen-users] Problem with Xen and OCFS2

[Gonçalo Borges <goncalo@xxxxxx>]

Hi again...

It seems this is a known issue that will be fixed in OCFS2 1.6. Here is the feedback from OCFS2 list.

Cheers
Goncalo

So this is a known issue on OCFS2 1.4/(RH)EL5 combination. As in, this
will _work_ on OCFS2 1.2 on the same kernel and _should_ work with OCFS2
bundled with the mainline kernels. But not on the specific combination you
are using.

In short, the xm save/dump-core implementation in 2.6.18 is hacky. And that
hack conflicts with the code we've had to add to backport the fs to (RH)EL5.
To get this to work, we will need some kernel symbols exported.

But it is too late for that and we will not be addressing this issue. The
issue should be resolved by OCFS2 1.6.

Sunil

Gonçalo Borges wrote:
Hi...

ocfs2 and kernel versions?

[root@core19 ~]# uname -a
Linux core19.ncg.ingrid.pt 2.6.18-128.1.16.el5xen #1 SMP Tue Jun 30 07:06:24 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

[root@core19 ~]# rpm -qa | grep ocfs2
ocfs2-tools-1.4.2-1.el5
ocfs2-2.6.18-128.1.16.el5xen-1.4.2-1.el5
ocfs2console-1.4.2-1.el5

Cheers
Goncalo

On 08/21/2009 05:38 PM, Nick Couchman wrote:

I have exactly the same issue and have posted a couple of times on this list without any response.  I'm guessing there's something about file locking on OCFS2 that doesn't work quite right for the xm save process, but I could be wrong.  I'm interested to see if you get any hits on this thread that help to track down the problem...

-Nick

>>> On 2009/08/21 at 08:42, Gonçalo Borges<goncalo@xxxxxx> wrote:

Hi All...

I'm testing a Xen solution on an OCFS2 SAN to store VM images.

If I try to save a VM asking to store the file in any Dom0 local dir
(ex: /tmp) everything works fine, and I can properly restore the VM
afterwards. Nevertheless, It I try to save a VM asking to store the
saved file inside the OCFS2 SAN, it fails with the following messages in
xend.log

---*---

[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:89) [xc_save]:
/usr/lib64/xen/bin/xc_save 26 9 0 0 0
[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:322) suspend
[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:92) In
saveInputHandler suspend
[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:94) Suspending 9 ...
[2009-08-21 14:45:25 xend.XendDomainInfo 9720] DEBUG
(XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch
[2009-08-21 14:45:25 xend.XendDomainInfo 9720] DEBUG
(XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch
[2009-08-21 14:45:25 xend.XendDomainInfo 9720] INFO (XendDomainInfo:994)
Domain has shutdown: name=migrating-one-0 id=9 reason=suspend.
[2009-08-21 14:45:25 xend 9720] INFO (XendCheckpoint:99) Domain 9 suspended.
[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:108) Written done
[2009-08-21 14:45:25 xend 9720] INFO (XendCheckpoint:351) Had 0
unexplained entries in p2m table
[2009-08-21 14:45:25 xend 9720] INFO (XendCheckpoint:351) Saving memory
pages: iter 1   0%ERROR Internal error: Error when writing to state file
(5) (errno 14)
[2009-08-21 14:45:25 xend 9720] INFO (XendCheckpoint:351) Save exit rc=1
[2009-08-21 14:45:25 xend 9720] ERROR (XendCheckpoint:133) Save failed
on domain one-0 (9).
Traceback (most recent call last):
   File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 110, in save
     forkHelper(cmd, fd, saveInputHandler, False)
   File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 339, in forkHelper
     raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 26 9 0 0 0 failed

---*---

It seems I'm not the only one complaining about this issue, according to
the following threads:

http://lists.xensource.com/archives/html/xen-users/2009-04/msg00670.html
http://lists.xensource.com/archives/html/xen-users/2008-09/msg00948.html

I wonder is there is some workaround for the problem?

Cheers
Goncalo

---

<br><hr>
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