vzdump and nfs:on

M

muzzol

Active Member
Dec 2, 2009
43
0
26
hi,

one of my dumps is failing:

Code: 
[COLOR=#000000][FONT=monospace]10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:23 INFO: suspend... 
10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:26 INFO: Can not suspend container: Resource temporarily unavailable 
10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:26 INFO: Error: foreign process 15195/21339(lockd) inside CT (e.g. vzctl enter or vzctl exec). 
10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:26 INFO: Error: suspend is impossible now. 
10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:26 INFO: Error: foreign process 15195/21339(lockd) inside CT (e.g. vzctl enter or vzctl exec). 
10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:26 INFO: Error: suspend is impossible now. 
10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:26 INFO: Error: foreign process 15195/21339(lockd) inside CT (e.g. vzctl enter or vzctl exec). 
10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:26 INFO: Error: suspend is impossible now. 
10012: [/FONT][/COLOR][COLOR=#00008B][FONT=monospace]Nov 12 12[/FONT][/COLOR][COLOR=#000000][FONT=monospace]:29:26 INFO: Checkpointing failed 
10012: [/FONT][/COLOR][COLOR=red][FONT=monospace][COLOR=#00008B]Nov 12 12[/COLOR]:29:29 ERROR: Backup of VM 10012 failed - command 'vzctl --skiplock chkpnt 10012 --suspend' failed with exit code 16[/FONT][/COLOR]

seems that lockd blocks suspending CT.

rest of CTs ara suspending ok, so i'm pretty surt that is nfs what is interfering with vzdump.

doesn't vzdump take care of nfs: on option? is this a known limitation or a bug?

in case I can't avoid this issue, is there any way to execute a pre script on the CT before dumping? this way I could manualy umount the nfs resource and mount it after performing the backup.
 
do you run any

vzctl enter or vzctl exec?
 
do you mean if I keep those running?

I usually use vzctl enter when preparing container, but once i've settled up i just connect through ssh.
 
An easy solution would be to use 'stop' or 'snapshot' mode for the backup (instead of 'suspend' mode)
 
dietmar said:
An easy solution would be to use 'stop' or 'snapshot' mode for the backup (instead of 'suspend' mode)
Click to expand...

ok, that could be a workaround. but I still would like to know if this limitation is by design, a bug or something else.
 
post the output of 'pveversion -v'
 
Code: 
# pveversion -v
pve-manager: 1.8-17 (pve-manager/1.8/5948)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.26-1pve4
vzdump: 1.2-12
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-3
ksm-control-daemon: 1.0-5
 
You must log in or register to reply here.
Top Bottom