Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 170630

vzdump: no such volume

$
0
0
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)
Code:

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
Code:

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
Code:

  --- Logical volume ---
  LV Path                /dev/vg01/vm-209-disk-1
  LV Name                vm-209-disk-1
  VG Name                vg01
  LV UUID                iBCwvK-4dhf-hITR-FQpT-swgM-7gZI-aHXovz
  LV Write Access        read/write
  LV Creation host, time hv02, 2012-10-15 10:44:00 +0200
  LV Status              available
  # open                1
  LV Size                18,00 GiB
  Current LE            4608
  Segments              1
  Allocation            inherit
  Read ahead sectors    auto
  - currently set to    256
  Block device          253:4



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

Trying to move disk give this error
Code:

TASK ERROR: storage migration failed: storage definintion has no path
Proxmox is up-to-date
Code:

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.

Viewing all articles
Browse latest Browse all 170630

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>