create storage failed: got lock request timeout (500)

chalan

Member
Mar 16, 2015
119
4
16
please help, i created a dir storage for backup in /mnt/backup i didnt realize that there are not enought disk space... i run backup, it ended with this error:

Code:
INFO: status: 36% (61855105024/171798691840), sparse 4% (8253263872), duration 4884, 10/10 MB/s

gzip: stdout: No space left on device
INFO: status: 36% (63489572864/171798691840), sparse 4% (8283189248), duration 5062, 9/9 MB/s
ERROR: vma_queue_write: write erINFO: unable to open file '/etc/pve/nodes/proxmox/qemu-server/104.conf.tmp.1044035' - Input/output error
ERROR: Backup of VM 104 failed - vma_queue_write: write error - Broken pipe

after that i cant create another storage, or edit/delete the old one... what should i do to make it right? thank you very much...

Code:
root@proxmox:~# df -h
Filesystem  Size  Used Avail Use% Mounted on
udev  10M  0  10M  0% /dev
tmpfs  1,6G  388K  1,6G  1% /run
/dev/mapper/pve-root  95G  2,1G  88G  3% /
tmpfs  5,0M  0  5,0M  0% /run/lock
tmpfs  3,2G  28M  3,2G  1% /run/shm
/dev/mapper/pve-data  792G  293G  500G  37% /var/lib/vz
/dev/md0  494M  59M  410M  13% /boot
/dev/fuse  30M  16K  30M  1% /etc/pve

Code:
root@proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.2-136 (running kernel: 2.6.32-32-pve)
pve-manager: 3.3-1 (running version: 3.3-1/a06c9f73)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-29-pve: 2.6.32-126
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.1-34
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-5
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
Last edited:
i have to reboot the machine and than remove "lock: backup" from /etc/pve/qemu-server/104.conf

was thare any solution without reboot?