Can not suspend VE: Resource temporarily unavailable [message #21877] |
Wed, 17 October 2007 11:53  |
piavlo
Messages: 159 Registered: January 2007
|
Senior Member |
|
|
Hi, I can't migrate a VE since i have
lockd process which is seen only inside the VE itself.
If i run ps in HN i can't see this lockd process. Why?
This process is started only if mount nfs filesystem
inside the VE.
If i unmount the nfs filesystems inside VE the migration is ok
How can i make live migration to a VE with nfs mounted filesystems?
projsrv1# vzmigrate --online -r no -v projsrv3 101
OPT:--online
OPT:-r
OPT:-v
OPT:projsrv3
Starting online migration of VE 101 on projsrv3
* status: started
Loading /etc/vz/vz.conf and /etc/vz/conf/101.conf files
Check IPs on destination node:
Preparing remote node
Copying config file
101.conf 100% 1852 1.8KB/s 00:00
Saved parameters for VE 101
Creating remote VE root dir
Creating remote VE private dir
Initializing remote quota
Quota init
Turning remote quota on
Syncing private
Live migrating VE
Suspending VE
Setting up checkpoint...
suspend...
Can not suspend VE: Resource temporarily unavailable
foreign process 15638/14614(lockd) inside VE (e.g. vzctl enter or vzctl exec).
suspend is impossible now.
foreign process 15638/14614(lockd) inside VE (e.g. vzctl enter or vzctl exec).
suspend is impossible now.
foreign process 15638/14614(lockd) inside VE (e.g. vzctl enter or vzctl exec).
suspend is impossible now.
Checkpointing failed
Error: Failed to suspend VE
[Updated on: Wed, 17 October 2007 11:53] Report message to a moderator
|
|
|
|
|
|
|
Re: Can not suspend VE: Resource temporarily unavailable [message #22116 is a reply to message #21957] |
Sun, 21 October 2007 07:46   |
piavlo
Messages: 159 Registered: January 2007
|
Senior Member |
|
|
Andrey Mirkin wrote on Thu, 18 October 2007 10:21 |
piavlo wrote on Thu, 18 October 2007 03:19 | Well this does not look like a good solution, since having all nfs
mounts for all VE in VE0 is not secure not. Can you explain why this is a problem to migrate the lockd process and if this will or can be fixed in future releases of OpenVZ?
And also why i can't see the lockd process in VE0?
|
Can you please give me an access to your node? Send credentials via PM if you can.
If you can't give me an access then please describe your configuration (post here VE config and commands you use to mount nfs inside a VE)
|
Hi Andrey,
It looks like lockd is not the real problem
i've tried just to suspend a VE and got that nfs
filesystems is not supported.
# vzctl chkpnt 102 --suspend
Setting up checkpoint...
suspend...
Can not suspend VE: Invalid argument
unsupported fs type nfs
Checkpointing failed
So even if i mount nfs with nolock option it's not going to help.
Also i've found http://bugzilla.openvz.org/show_bug.cgi?id=616
Are you planning to work on this enhancement in the near future,
or i can just forget about it?
Thanks
Alex
[Updated on: Sun, 21 October 2007 07:48] Report message to a moderator
|
|
|
|
|
Re: Can not suspend VE: Resource temporarily unavailable [message #22811 is a reply to message #21887] |
Sun, 04 November 2007 14:01  |
piavlo
Messages: 159 Registered: January 2007
|
Senior Member |
|
|
Hi Andrey,
Andrey Mirkin wrote on Wed, 17 October 2007 15:33 | Hello,
Please try to mount nfs in following way:
1. mount nfs in VE0
2. bind mount it on VE start (use VEID.mount script for this)
|
I've mounted the nfs partition in VE0 and bind mouted it in VE
root> cat /etc/vz/conf/102.mount
#!/bin/bash
mount -n --bind /users/staff /vz/root/102/users/staff
exit ${?}
It still gives the same error:
root> vzctl chkpnt 102 --suspend
Setting up checkpoint...
suspend...
Can not suspend VE: Invalid argument
unsupported fs type nfs
Checkpointing failed
The nfs mount is not listed in VE0 mtab, but is listed in VE102
mtab. And is listed both on VE0 & VE102 /proc/mounts.
I've tried to remove the nfs mount from VE102 mtab but it did not
help.
So it looks like there is no way to checkpoint or migrate a VE
which acts like an nfs client. Or should it still work with bind mounts?
Thanks
Alex
|
|
|