vzdump "unable to deactivate <lvname>-real"

H

hk@

Renowned Member
Feb 10, 2010
248
8
83
Vienna
kapper.net
Hi
in the backuplog I see:

75004: Jul 09 00:50:23 INFO: Starting Backup of VM 75004 (qemu)
75004: Jul 09 00:50:24 INFO: running
75004: Jul 09 00:50:24 INFO: status = running
75004: Jul 09 00:50:24 INFO: backup mode: snapshot
75004: Jul 09 00:50:24 INFO: ionice priority: 7
75004: Jul 09 00:50:24 INFO: Logical volume "vzsnap-k75-0" created
75004: Jul 09 00:50:24 INFO: creating archive '/mnt/pve/store02_kXX_backup/vzdump-qemu-75004-2011_07_09-00_50_23.tgz'
75004: Jul 09 00:50:24 INFO: adding '/mnt/pve/store02_kXX_backup/vzdump-qemu-75004-2011_07_09-00_50_23.tmp/qemu-server.conf' to archive ('qemu-server.conf')
75004: Jul 09 00:50:24 INFO: adding '/dev/SASRAID5/vzsnap-k75-0' to archive ('vm-disk-virtio0.raw')
75004: Jul 09 00:57:32 INFO: Total bytes written: 8776349696 (19.55 MiB/s)
75004: Jul 09 00:57:33 INFO: archive file size: 3.23GB
75004: Jul 09 00:57:33 INFO: device-mapper: remove ioctl failed: Device or resource busy
75004: Jul 09 00:57:33 INFO: Unable to deactivate SASRAID5-vm--75004--disk--1-real (251:12)
75004: Jul 09 00:57:33 INFO: Logical volume "vzsnap-k75-0" successfully removed
75004: Jul 09 00:57:34 INFO: Finished Backup of VM 75004 (00:07:11)
Click to expand...

the storage for this VM resides in a lvm-volume named /dev/SASRAID5/vm-75004-disk-1, I have never seen this thing building itself to "-real" added at the end nor do I know why it might have failed to deactivate - and at the moment this thing isn't listed in lvscan:

Code: 
  ACTIVE            '/dev/SASRAID5/vm-72002-disk-1' [60.00 GB] inherit
  ACTIVE            '/dev/SASRAID5/vm-75001-disk-1' [20.00 GB] inherit
  ACTIVE            '/dev/SASRAID5/vm-75003-disk-1' [10.00 GB] inherit
  ACTIVE            '/dev/SASRAID5/vm-75002-disk-1' [10.00 GB] inherit
  ACTIVE            '/dev/SASRAID5/vm-75004-disk-1' [10.00 GB] inherit
  ACTIVE            '/dev/SASRAID5/vm-75005-disk-1' [10.00 GB] inherit
  ACTIVE            '/dev/pve/swap' [28.88 GB] inherit
  ACTIVE            '/dev/pve/root' [57.75 GB] inherit
  ACTIVE            '/dev/pve/data' [140.77 GB] inherit

pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.8-11
pve-kernel-2.6.35-1-pve: 2.6.35-11
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6

any thoughts are appreciated, this was the only "unable" log-entry though all kvm-instances are backuped in one job.

regards
hk
 
Looks the problem is related to removing the snapshot, but finally it was removed successfully. So I guess the backup is OK. I have never seen such message before. Please can you observe if it happens again next time?
 
Hi again,
I will look into it - and - I have to report another anomaly that I overlooked because it too says everything is fine - this happened during the same backup-job but two VMs before:

75002: Jul 09 00:39:56 INFO: Starting Backup of VM 75002 (qemu)
75002: Jul 09 00:39:56 INFO: running
75002: Jul 09 00:39:56 INFO: status = running
75002: Jul 09 00:39:56 INFO: backup mode: snapshot
75002: Jul 09 00:39:56 INFO: ionice priority: 7
75002: Jul 09 00:39:56 INFO: /dev/mapper/SASRAID5-vm--75002--disk--1-real: open failed: No such file or directory
75002: Jul 09 00:39:56 INFO: Logical volume "vzsnap-k75-0" created
75002: Jul 09 00:39:56 INFO: creating archive '/mnt/pve/store02_kXX_backup/vzdump-qemu-75002-2011_07_09-00_39_56.tgz'
75002: Jul 09 00:39:56 INFO: adding '/mnt/pve/store02_kXX_backup/vzdump-qemu-75002-2011_07_09-00_39_56.tmp/qemu-server.conf' to archive ('qemu-server.conf')
75002: Jul 09 00:39:56 INFO: adding '/dev/SASRAID5/vzsnap-k75-0' to archive ('vm-disk-virtio0.raw')
75002: Jul 09 00:42:12 INFO: Total bytes written: 1736728576 (12.18 MiB/s)
75002: Jul 09 00:42:12 INFO: archive file size: 623MB
75002: Jul 09 00:42:13 INFO: Logical volume "vzsnap-k75-0" successfully removed
75002: Jul 09 00:42:13 INFO: Finished Backup of VM 75002 (00:02:17)
Click to expand...


RAID-Controller claims everything is fine:
megaclisas-status
-- Controller informations --
-- ID | Model
c0 | MegaRAID SAS 8708ELP


-- Arrays informations --
-- ID | Type | Size | Status | InProgress
c0u0 | RAID1 | 232G | Optimal | None
c0u1 | RAID5 | 557G | Optimal | None
c0u2 | RAID1 | 1817G | Optimal | None
Click to expand...

hmmm...
 
Last edited:
well,
I could have searched for "failed" before in the mail-folder where all the "backup successfull" mails are stored.

therefore I can say - this has happened before once:

75002: Jul 08 03:40:03 INFO: Starting Backup of VM 75002 (qemu)
75002: Jul 08 03:40:03 INFO: running
75002: Jul 08 03:40:03 INFO: status = running
75002: Jul 08 03:40:03 INFO: backup mode: snapshot
75002: Jul 08 03:40:03 INFO: ionice priority: 7
75002: Jul 08 03:40:03 INFO: Logical volume "vzsnap-k75-0" created
75002: Jul 08 03:40:03 INFO: creating archive '/mnt/pve/store02_kXX_backup/vzdump-qemu-75002-2011_07_08-03_40_03.tgz'
75002: Jul 08 03:40:03 INFO: adding '/mnt/pve/store02_kXX_backup/vzdump-qemu-75002-2011_07_08-03_40_03.tmp/qemu-server.conf' to archive ('qemu-server.conf')
75002: Jul 08 03:40:03 INFO: adding '/dev/SASRAID5/vzsnap-k75-0' to archive ('vm-disk-virtio0.raw')
75002: Jul 08 03:42:20 INFO: Total bytes written: 1738413568 (12.09 MiB/s)
75002: Jul 08 03:42:20 INFO: archive file size: 623MB
75002: Jul 08 03:42:21 INFO: device-mapper: remove ioctl failed: Device or resource busy
75002: Jul 08 03:42:21 INFO: Unable to deactivate SASRAID5-vm--75002--disk--1-real (251:10)
75002: Jul 08 03:42:21 INFO: Logical volume "vzsnap-k75-0" successfully removed
75002: Jul 08 03:42:21 INFO: Finished Backup of VM 75002 (00:02:18)


 
You must log in or register to reply here.
Top Bottom