[pve-devel] VZDump issues with lvm

Adrian Almenar adrian at almenar.nl
Tue May 13 13:13:35 CEST 2014


Hi everyone,

Last days, im having a really strange issue. I have some vz containers, and they are backuped every day at 3 AM.

The task was created using proxmox web interface (Simple as All VMS) option. (Backup is made on an external disk (USB 3.0), mounted in /media/backups)

Today (this is the second time that happens) i find my root partition totally full, checkout the logs and it was file by the kern.log file.

The error printed constanty is:

ext3_orphan_cleanup: deleting unreferenced inode 25846833
ext3_orphan_cleanup: deleting unreferenced inode 25846833
ext3_orphan_cleanup: deleting unreferenced inode 25846833
ext3_orphan_cleanup: deleting unreferenced inode 25846833
ext3_orphan_cleanup: deleting unreferenced inode 25846833
ext3_orphan_cleanup: deleting unreferenced inode 25846833

(Yes it’s always the same inode)

There’s only a process locked by this:

mount -n -t ext3 /dev/pve/vzsnap-nodename-0 /mnt/vzsnap0


I have tried forcing the lvmremove (But all i get is a lock):

# lvremove --force /dev/pve/vzsnap-nodename-0
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  device-mapper: remove ioctl on  failed: Device or resource busy
  Unable to deactivate pve-vzsnap--nodename--0 (253:2)
  Unable to deactivate logical volume "vzsnap-nodename-0"


Also, tried to use dmsetup to unmount the volume using:

dmsetup remove -f --retry /dev/pve/vzsnap-nodename-0

But command still does not return anything.

Here i include pvevefsion —verbose for more information:

# pveversion --verbose
proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-26-pve: 2.6.32-114
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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1


I have search the forums, also on openvz.org bugzilla but haven’t found anything.

Any thoughts ?


Regards,

Adrian


More information about the pve-devel mailing list