LXC backup error

[marigo]

I have an issue when a -stop lxc backup starts. This is the log Proxmox produces. I had no issues with Proxmox4.0.

INFO: starting new backup job: vzdump 106 --mode stop --compress lzo --node proxmox --remove 0 --storage USB
INFO: Starting Backup of VM 106 (lxc)
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: stopping vm
INFO: creating archive '/mnt/usb/dump/vzdump-lxc-106-2016_01_11-21_46_14.tar.lzo'
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
      missing codepage or helper program, or other error

      In some cases useful info is found in syslog - try
      dmesg | tail or so.
umount: /mnt/vzsnap0/: not mounted
command 'umount -l -d /mnt/vzsnap0/' failed: exit code 32
INFO: restarting vm
INFO: vm is online again after 34 seconds
ERROR: Backup of VM 106 failed - command 'mount -o loop /var/lib/vz/images/106/vm-106-disk-1.raw /mnt/vzsnap0/' failed: exit code 32
INFO: Backup job finished with errors
TASK ERROR: job errors

I've installed the lxc on another Proxmox machine (also 4.1) but it gives me the same output when a backup starts of the container.

I can do a -snapshot backup of the lxc, but it fails also after two or three times.
Is there a solution for this issue?

 

[dietmar]

What is the output of

# pveversion -v

(please make sure you run the latest version).

 

[marigo]

Here is the output requested:

root@proxmox2:~# pveversion -v
proxmox-ve: 4.1-28 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-2 (running version: 4.1-2/78c5f4a2)
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-42-pve: 2.6.32-165
pve-kernel-4.2.6-1-pve: 4.2.6-28
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-29
qemu-server: 4.0-42
pve-firmware: 1.1-7
libpve-common-perl: 4.0-42
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-18
pve-container: 1.0-35
pve-firewall: 2.0-14
pve-ha-manager: 1.0-16
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
root@proxmox2:~#

 

[dietmar]

please test with pve-container 1.0-36 or newer.

 

[windinternet]

What does this say?

file -s /var/lib/vz/images/106/vm-106-disk-1.raw

 

[marigo]

What does this say?

file -s /var/lib/vz/images/106/vm-106-disk-1.raw

root@proxmox2:~# file -s /var/lib/vz/images/106/vm-106-disk-1.raw
/var/lib/vz/images/106/vm-106-disk-1.raw: Linux rev 1.0 ext4 filesystem data, UUID=d404ee0a-0f60-4d38-8803-a61cfbf53168 (needs journal recovery) (extents) (large files) (huge files)
root@proxmox2:~#

 

[marigo]

Upgraded two Promox servers to pve-container: 1.0-37. Both are successful!

Thank you for your support!

INFO: starting new backup job: vzdump 103 --node proxmox2 --remove 0 --mode stop --compress lzo --storage USB2
INFO: Starting Backup of VM 103 (lxc)
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: stopping vm
INFO: creating archive '/mnt/usb2/dump/vzdump-lxc-103-2016_01_12-13_11_44.tar.lzo'
INFO: Total bytes written: 634869760 (606MiB, 41MiB/s)
INFO: archive file size: 311MB
INFO: restarting vm
INFO: vm is online again after 30 seconds
INFO: Finished Backup of VM 103 (00:00:30)
INFO: Backup job finished successfully
TASK OK

INFO: starting new backup job: vzdump 106 --node proxmox --mode stop --storage USB --compress lzo --remove 0
INFO: Starting Backup of VM 106 (lxc)
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: stopping vm
INFO: creating archive '/mnt/usb/dump/vzdump-lxc-106-2016_01_12-13_16_35.tar.lzo'
INFO: Total bytes written: 635156480 (606MiB, 32MiB/s)
INFO: archive file size: 311MB
INFO: restarting vm
INFO: vm is online again after 34 seconds
INFO: Finished Backup of VM 106 (00:00:34)
INFO: Backup job finished successfully
TASK OK

 

[windinternet]

needs journal recovery

Seems like you have a problem of the container not correctly shutting down. You could loop mount it and run fsck on it. You can make a copy of the file first for backup if you don't have a current backup.

losetup -f --show /var/lib/vz/images/106/vm-106-disk-1.raw
fsck /dev/loopx (x=number as shown from previous command output)
losetup -d /dev/loopx

Maybe try suspend backup mode instead of stop.

 

[marigo]

I just executed three times the backup via the "stop" feature. Everything looks fine now.

I have also executed your suggestion. The output shows "clean".

root@proxmox:~# losetup -f --show /var/lib/vz/images/106/vm-106-disk-1.raw
/dev/loop0
root@proxmox:~# fsck /dev/loop0
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/loop0: clean, 54224/262144 files, 223553/1048576 blocks
root@proxmox:~# losetup -d /dev/loop0

Thank you for your quick reply.