vzdump: no such volume

[sub1]

Hello all,

first, thanks for your fantastic product. I'm doing a test lab with latest proxmox version. All seems to work nice but I got some errors since yesterday when I want to backup VM or move a drive

I got this error on all VM (I tried with running or stopped VM)

root@proxmox02:~# vzdump 207 --remove 0 --mode snapshot --compress lzo --storage Backups0402


INFO: starting new backup job: vzdump 207 --remove 0 --mode snapshot --compress lzo --storage Backups0402
INFO: Starting Backup of VM 207 (qemu)
INFO: status = running
INFO: update VM 207: -lock backup
ERROR: Backup of VM 207 failed - no such volume 'VM:vm-207-disk-1'
INFO: Backup job finished with errors
job errors

here is the config file for VM 207

balloon: 256
bootdisk: ide0
cores: 1
ide0: VM:vm-207-disk-1,size=8196M
ide2: none,media=cdrom,size=169M
memory: 512
name: SRV-TEST2
net0: virtio=FE:D4:BC:AF:4E:DF,bridge=vmbr1
onboot: 1
ostype: l26
sockets: 1
startup: order=1

lv display find associated LV
root@proxmox02:/etc/pve/qemu-server# lvdisplay

  --- Logical volume ---
  LV Path                /dev/vg01/vm-207-disk-1
  LV Name                vm-207-disk-1
  VG Name                vg01
  LV UUID                aWUPOt-3tg3-oPRo-f9ym-gDWE-YVK5-jSB7hR
  LV Write Access        read/write
  LV Creation host, time hv02, 2012-10-13 19:17:47 +0200
  LV Status              available
  # open                 1
  LV Size                8,00 GiB
  Current LE             2049
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

And I'm able to stop/start this VM.

Trying to move disk give this error

[COLOR=#000000][FONT=tahoma]TASK ERROR: storage migration failed: storage definintion has no path[/FONT][/COLOR]

Proxmox is up-to-date

root@proxmox02:~# pveversion -v
proxmox-ve-2.6.32: 3.1-111 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-13 (running version: 3.1-13/262cf0b8)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.0-2
pve-cluster: 3.0-7
qemu-server: 3.1-3
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-12
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

Can you please help to solve this issue ?

Regards.

Edit : I've posted a wrong LV configuration

 

[ivensiya]

I have same problem after upgrade tonight.

 

[dietmar]

Please can you also post the storage configuration /etc/pve/storage.cfg?

 

[ivensiya]

dir: local
path /var/lib/vz
content images,vztmpl,backup,rootdir
maxfiles 7


glusterfs: Gluster
volume gluster
path /mnt/pve/Gluster
content images,iso,vztmpl,backup
server localhost
maxfiles 7


lvm: VMs
vgname drbdvg
shared
content images

 

[dietmar]

dir: local
path /var/lib/vz
content images,vztmpl,backup,rootdir
maxfiles 7


glusterfs: Gluster
volume gluster
path /mnt/pve/Gluster
content images,iso,vztmpl,backup
server localhost
maxfiles 7


lvm: VMs
vgname drbdvg
shared
content images

There is no storage called 'VM'!

 

[sub1]

Please can you also post the storage configuration /etc/pve/storage.cfg?

Hello Dietmar,

root@[COLOR=#333333]proxmox02[/COLOR]:~# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content iso,vztmpl,rootdir
        maxfiles 0


lvm: VM
        vgname vg01
        content images


dir: Backups
        path /var/lib/vz/dump
        content images,backup
        maxfiles 3

I have the "VM" storage.

 

[ivensiya]

my problem with storage VMs. It's the same problem like VM

 

[dietmar]

What is the output of

# pvesm list VM

 

[dietmar]

OK - I finally found the bug! Will upload a fix later today.

update: the fix is already uploaded

 

[ivensiya]

Thank you dietmar!
Now everything is working!

 

[sub1]

OK - I finally found the bug! Will upload a fix later today.

update: the fix is already uploaded

Hi,

I confirm that all is now working fine.

Many thanks.