| 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 |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
