Another NFS-related issue (vzdump --suspend can't stop lockd) [message #33274] |
Fri, 03 October 2008 09:19 |
fatbrother
Messages: 12 Registered: September 2008 Location: Novosibirsk, Russia
|
Junior Member |
|
|
I have same setup as in my previous posting ( http://forum.openvz.org/index.php?t=tree&goto=33262& #msg_33262):
HN debian/FZA 2.6.18-12-fza-amd64 kernel, Debian Etch, vzctl 3.0.22-1dso1,
VE Centos 5.2, nfstools 1.0.9, has NFS mount.
I'm trying to do vzdump --suspend --exclude-path /home VE.
(BTW, do I ever need --exclude-path, won't it exclude NFS mount automatically?)
First sync goes OK, but on second sync I get:
INFO: suspend vps
Setting up checkpoint...
suspend...
Can not suspend VE: Resource temporarily unavailable
Error: foreign process 22159/21135(lockd) inside VE (e.g. vzctl enter or vzctl exec).
Error: suspend is impossible now.
Error: foreign process 22159/21135(lockd) inside VE (e.g. vzctl enter or vzctl exec).
Error: suspend is impossible now.
Error: foreign process 22159/21135(lockd) inside VE (e.g. vzctl enter or vzctl exec).
Error: suspend is impossible now.
Checkpointing failed
As far as I understand, that's NFS lockd, right?
What should I do? Not using lockd is unacceptable for several reasons. Umounting NFS renders VE unusable, so it'd be as good as vzdump --stop. If you suggest using vzdump --checkpoint, I have another issue for ya.
|
|
|
|
Re: Another NFS-related issue (vzdump --suspend can't stop lockd) [message #33288 is a reply to message #33279] |
Fri, 03 October 2008 17:40 |
fatbrother
Messages: 12 Registered: September 2008 Location: Novosibirsk, Russia
|
Junior Member |
|
|
maratrus wrote on Fri, 03 October 2008 22:49 | Hi,
How lockd was started? Did you start it from inside the HN like "vzctl exec ..."?
|
No. I hit this problem, stopped the container, did the backup and started the container again. And run vzdump again to post correct text of error message to the forum. So all this was after a clean container restart.
|
|
|
|