Hello,
I got an critical issue with vzdump. I start vzdump with a cronjob and the system gets a kernel panic.
syslog:
Apr 2 04:28:37 system-1 vzdump[469932]: INFO: starting new backup job: vzdump 100013 --quiet --bwlimit 20480 --dumpdir /mnt/pve/storage/vs-13/backup/ --exclude-path var/lib/mysql/.+
Apr 2 04:28:37 system-1 vzdump[469932]: INFO: Starting Backup of VM 100013 (openvz)
vzdump.log:
Apr 02 04:28:37 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-system-1-0')<-- and it hangs
After restarting the system fsck started with these logs:
/dev/pve/data: Clearing orphaned inode 76032690 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 76032689 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 76032756 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 76032755 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 76032754 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 75694766 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 75694765 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 75694764 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 75694763 (uid=106, gid=110, mode=0100600, size=376)
/dev/pve/data: Clearing orphaned inode 75694762 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 75743246 (uid=0, gid=0, mode=0100644, size=0)
/dev/pve/data: Clearing orphaned inode 76046418 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76046417 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76046416 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76046415 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76046402 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76032654 (uid=0, gid=0, mode=0100644, size=0)
/dev/pve/data: clean, 1227982/114180096 files, 22693734/456692736 blocks
/dev/sda1: recovering journal
/dev/sda1: clean, 33/32768 files, 15217/131072 blocks
system-1:~# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-2
pve-kernel-2.6.32-7-pve: 2.6.32-55+ovzfix-2
qemu-server: 1.1-32
pve-firmware: 1.0-15
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
I can not find the issue. How I can solve the failure. It happens 2 times last 2 weeks.
Best regards,
Alex
I got an critical issue with vzdump. I start vzdump with a cronjob and the system gets a kernel panic.
syslog:
Apr 2 04:28:37 system-1 vzdump[469932]: INFO: starting new backup job: vzdump 100013 --quiet --bwlimit 20480 --dumpdir /mnt/pve/storage/vs-13/backup/ --exclude-path var/lib/mysql/.+
Apr 2 04:28:37 system-1 vzdump[469932]: INFO: Starting Backup of VM 100013 (openvz)
vzdump.log:
Apr 02 04:28:37 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-system-1-0')<-- and it hangs
After restarting the system fsck started with these logs:
/dev/pve/data: Clearing orphaned inode 76032690 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 76032689 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 76032756 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 76032755 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 76032754 (uid=1000, gid=1000, mode=0100600, size=268435456)
/dev/pve/data: Clearing orphaned inode 75694766 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 75694765 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 75694764 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 75694763 (uid=106, gid=110, mode=0100600, size=376)
/dev/pve/data: Clearing orphaned inode 75694762 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 75743246 (uid=0, gid=0, mode=0100644, size=0)
/dev/pve/data: Clearing orphaned inode 76046418 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76046417 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76046416 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76046415 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76046402 (uid=106, gid=110, mode=0100600, size=0)
/dev/pve/data: Clearing orphaned inode 76032654 (uid=0, gid=0, mode=0100644, size=0)
/dev/pve/data: clean, 1227982/114180096 files, 22693734/456692736 blocks
/dev/sda1: recovering journal
/dev/sda1: clean, 33/32768 files, 15217/131072 blocks
system-1:~# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-2
pve-kernel-2.6.32-7-pve: 2.6.32-55+ovzfix-2
qemu-server: 1.1-32
pve-firmware: 1.0-15
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
I can not find the issue. How I can solve the failure. It happens 2 times last 2 weeks.
Best regards,
Alex