Ubuntu 22.04 Container gets stuck while backing up

comexos

New Member
Apr 6, 2021
1
0
1
42
Hello,
we started rolling out Ubuntu 22.04 containers using the Proxmox provided ubuntu-22.04-standard_22.04-1_amd64.tar.zst images.
When backing up the machines the process gets stuck while creating the storage snapshot 'vzdump'. When the machines are stopped (backup mode "stop", the backup seems to work fine. When the machines are running (backup mode snapshot), the process gets stuck:

Code:
INFO: starting new backup job: vzdump --node px03 --pool Ubuntu22 --mailnotification always --all 0 --notes-template '{{guestname}}' --mode snapshot --prune-backups 'keep-last=1' --storage cephfs --mailto admin@test.com --compress zstd
INFO: Starting Backup of VM 115 (lxc)
INFO: Backup started at 2022-08-02 11:41:45
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: test1.test-cloud.at
INFO: including mount point rootfs ('/') in backup
INFO: creating vzdump archive '/mnt/pve/cephfs/dump/vzdump-lxc-115-2022_08_02-11_41_45.tar.zst'
/dev/rbd2
INFO: Total bytes written: 6207283200 (5.8GiB, 27MiB/s)
INFO: archive file size: 2.46GB
INFO: adding notes to backup
INFO: prune older backups with retention: keep-last=1
INFO: pruned 0 backup(s)
INFO: Finished Backup of VM 115 (00:03:45)
INFO: Backup finished at 2022-08-02 11:45:30
INFO: Starting Backup of VM 121 (lxc)
INFO: Backup started at 2022-08-02 11:45:30
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: ALT.cloud.test-cloud.at
INFO: including mount point rootfs ('/') in backup
INFO: creating vzdump archive '/mnt/pve/cephfs/dump/vzdump-lxc-121-2022_08_02-11_45_30.tar.zst'
/dev/rbd3
INFO: Total bytes written: 20072499200 (19GiB, 35MiB/s)
INFO: archive file size: 8.75GB
INFO: adding notes to backup
INFO: prune older backups with retention: keep-last=1
INFO: pruned 0 backup(s)
INFO: Finished Backup of VM 121 (00:09:28)
INFO: Backup finished at 2022-08-02 11:54:58
INFO: Starting Backup of VM 126 (lxc)
INFO: Backup started at 2022-08-02 11:54:59
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: ALT.cloud.test-cloud.eu
INFO: including mount point rootfs ('/') in backup
INFO: creating vzdump archive '/mnt/pve/cephfs/dump/vzdump-lxc-126-2022_08_02-11_54_59.tar.zst'
/dev/rbd6
INFO: Total bytes written: 11326392320 (11GiB, 36MiB/s)
INFO: archive file size: 6.97GB
INFO: adding notes to backup
INFO: prune older backups with retention: keep-last=1
INFO: removing backup 'cephfs:backup/vzdump-lxc-126-2022_07_17-00_44_00.tar'
INFO: pruned 1 backup(s) not covered by keep-retention policy
INFO: Finished Backup of VM 126 (00:05:08)
INFO: Backup finished at 2022-08-02 12:00:07
INFO: Starting Backup of VM 133 (lxc)
INFO: Backup started at 2022-08-02 12:00:07
INFO: status = running
INFO: CT Name: cloud.test-cloud.ch
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'

Code:
cat /etc/pve/lxc/133.conf
arch: amd64
cores: 1
features: nesting=1
hostname: cloud.test-cloud.ch
memory: 2048
nameserver: 8.8.8.8
net0: name=eth0,bridge=vmbr0,firewall=1,gw=91.x.x.x,gw6=fe80::2:1,hwaddr=xxx,ip=91.x.x.x/26,ip6=2a10:xxx::1/64,rate=12,tag=1002,type=veth
ostype: ubuntu
rootfs: SSDPool:vm-133-disk-0,size=200G
swap: 2048
unprivileged: 1

[vzdump]
#vzdump backup snapshot
arch: amd64
cores: 1
features: nesting=1
hostname: cloud.test-cloud.ch
memory: 2048
nameserver: 8.8.8.8
net0: name=eth0,bridge=vmbr0,firewall=1,gw=91.x.x.x,gw6=fe80::2:1,hwaddr=xxx,ip=91.x.x.x/26,ip6=2a10:xxx::1/64,rate=12,tag=1002,type=veth
ostype: ubuntu
rootfs: SSDPool:vm-133-disk-0,size=200G
snapstate: prepare
snaptime: 1659434408
swap: 2048
unprivileged: 1

These are all Ubuntu 22.04 Containers from the same template. The data is stored on a Ceph Pool. The last machine "cloud.test-cloud.ch" gets stuck while creating the storage snapshot. We never experienced that behaviour with Ubuntu 20.04 or Debian containers. After it gets stuck, the container is locked, the backup process is frozen and the container can't be started again unless we reboot the whole proxmox node it is running on.

Did anyone experience this issue or any suggestions?
Thanks Tom
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!