Guest-agent fs-freeze command breaks the system on backup

robertb

Member
Apr 4, 2017
18
1
23
28
Germany
Hey guys,

did anyone manage to find a cause for this?
Happens to me too since a few weeks now. Some virtual machines will at random switch to read only mode and present exact the same problem after rebooting. Seems to happen after taking a snapshot backup to pbs.
However, after running fsck manually it seems to be fine again.
 
  • Like
Reactions: drnoelkelly

cglmicro

Member
Oct 12, 2020
66
8
8
49
Hi Soltecsis.

You are right, for the first time I'm able to do a backup of all my VMs, thanks.
 

ynorecex

New Member
Jun 13, 2021
1
0
1
35
Same issue here, cPanel 96.09 on Cloudlinux 8.3
Proxmox 6.4-8
PBS 1.1-9

I had run a manual backup of the VPS on PBS and the VM froze, I needed to unlock by the host shell to be able to restart the VM.

Then I had to buy new underwear.
 

Rawthink

Active Member
Apr 22, 2015
30
0
26
Bump. This is still an issue. I just tried a brand new install of Cloud Linux. Backups worked fine with the guest agent enabled... Then I installed cpanel. Now same problem. Totally freezes the VM and requires a stop and start...

Any chance we can find the cause and correct this?
 
Mar 19, 2018
146
18
38
I don't like the idea of the guest agent causing problems -- or of some third party change or package causing problems with the guest agent, which then causes problems with backups.

Its a shame nobody has managed to narrow this down. I find it very worrying.
 
  • Like
Reactions: drnoelkelly
Jan 16, 2009
169
14
38
Inside CentOS 7, when we install the guest-agent there is a file: /etc/qemu-ga/fsfreeze-hook

Code:
#!/bin/sh

# This script is executed when a guest agent receives fsfreeze-freeze and
# fsfreeze-thaw command, if it is specified in --fsfreeze-hook (-F)
# option of qemu-ga or placed in default path (/etc/qemu/fsfreeze-hook).
# When the agent receives fsfreeze-freeze request, this script is issued with
# "freeze" argument before the filesystem is frozen. And for fsfreeze-thaw
# request, it is issued with "thaw" argument after filesystem is thawed.

LOGFILE=/var/log/qga-fsfreeze-hook.log
FSFREEZE_D=$(dirname -- "$0")/fsfreeze-hook.d

# Check whether file $1 is a backup or rpm-generated file and should be ignored
is_ignored_file() {
    case "$1" in
        *~ | *.bak | *.orig | *.rpmnew | *.rpmorig | *.rpmsave | *.sample)
            return 0 ;;
    esac
    return 1
}

# Iterate executables in directory "fsfreeze-hook.d" with the specified args
[ ! -d "$FSFREEZE_D" ] && exit 0
for file in "$FSFREEZE_D"/* ; do
    is_ignored_file "$file" && continue
    [ -x "$file" ] || continue
    printf "$(date): execute $file $@\n" >>$LOGFILE
    "$file" "$@" >>$LOGFILE 2>&1
    STATUS=$?
    printf "$(date): $file finished with status=$STATUS\n" >>$LOGFILE
done

exit 0

It's something here we can tune to fix the issue?
 

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 your own in 60 seconds.

Buy now!