VM backup freezed at fs-freeze command

bly

Member
Mar 15, 2024
54
13
8
Hi, one VM were stuck while backing up at line "INFO: issuing guest-agent 'fs-freeze' command" so I did stop the process and you see what followed next.


Code:
INFO: starting new backup job: vzdump 412 --notes-template '{{guestname}}' --storage SG8T --prune-backups 'keep-all=1' --mode snapshot --fleecing 0 --quiet 1
INFO: Starting Backup of VM 412 (qemu)
INFO: Backup started at 2024-11-12 13:45:05
INFO: status = running
INFO: VM Name: asteroid
INFO: include disk 'virtio0' 'SSD-52X:vm-412-disk-0' 600G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: pending configuration changes found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/412/2024-11-12T12:45:05Z'
INFO: issuing guest-agent 'fs-freeze' command
closing with read buffer at /usr/share/perl5/IO/Multiplex.pm line 927.
ERROR: interrupted by signal
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '9a77cb8e-31cd-495f-8977-9457da4f1745'
INFO: resuming VM again
INFO: virtio0: dirty-bitmap status: OK (29.8 GiB of 600.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 29.8 GiB dirty of 600.0 GiB total
INFO:   1% (440.0 MiB of 29.8 GiB) in 3s, read: 146.7 MiB/s, write: 146.7 MiB/s

Any hint to figure why it was stuck? It is a scheduled backup running every 15 minutes and usually ending in 1-2 minutes.

After stopping the backup I did a "qm unlock 412" command to unlock it.

The next backup gone ok:

1731417501938.png
 
Last edited:
Same issues here, we're using PBS to backup and the specific VM needed a manual intervention (qm guest cmd xxx fsfreeze-thaw) to be functional again.

Code:
INFO: Starting Backup of VM 277 (qemu)
INFO: Backup started at 2024-12-04 01:38:13
INFO: status = running
INFO: VM Name: xxxx.xxxx.com
INFO: include disk 'scsi0' 'ceph-nvme-volumes:vm-277-disk-0' 20G
INFO: include disk 'scsi1' 'ceph-nvme-volumes:vm-277-disk-1' 140G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/277/2024-12-04T00:38:13Z'
INFO: enabling encryption
INFO: issuing guest-agent 'fs-freeze' command
closing with read buffer at /usr/share/perl5/IO/Multiplex.pm line 927.
ERROR: interrupted by signal
INFO: issuing guest-agent 'fs-thaw' command

Inside the Guest (Debian 11), in /var/log/messages

Code:
Dec  4 01:38:14 xxxxx01 qemu-ga: info: guest-ping called
Dec  4 01:38:14 xxxxx01 qemu-ga: info: guest-fsfreeze called

It seems that the freeze command is succesfull, but the thaw command is not executed afterwards which caused the VM to stay in freezed state.

Guest config

Code:
agent: enabled=1,fstrim_cloned_disks=1,freeze-fs-on-backup=1
bios: seabios
boot: order=scsi0
cores: 8
cpu: host
ide0: none,media=cdrom
memory: 4096
meta: creation-qemu=9.0.2,ctime=1726555571
name: xxxx01.xxx.com
net0: virtio=00:50:56:b8:71:bc,bridge=public
ostype: l26
scsi0: ceph-nvme-volumes:vm-277-disk-0,iothread=1,size=20G
scsi1: ceph-nvme-volumes:vm-277-disk-1,iothread=1,size=140G
scsihw: virtio-scsi-single
smbios1: uuid=e2dd1343-a784-4714-bf34-1f653a1b4a7d
sockets: 1
vmgenid: 53d7ebae-2653-4a95-89ee-745a085abac9

Versions:

Code:
root@compute03:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.8-3-pve-signed: 6.8.8-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-6-pve-signed: 6.5.11-6
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
dnsmasq: 2.89-1
frr-pythontools: 8.5.2-1+pve1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
openvswitch-switch: 3.1.0-2+deb12u1
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1
 
Last edited:
Hello,

I have the same issue. In my case, this error occurs only with Linux VMs.

For example, Windows VMs (with the QEMU agent also installed) don’t have this problem. I haven’t found the solution yet. The QEMU agent is installed on the machine, but when I start the backup, the machine freezes.

Any solution or sugestion?

At moment I disabled the option of freeze-fs-on-backup :(

Regards,

Adriano