A Hostinger VPS freezes or becomes unresponsive during backups when the QEMU guest agent can’t finish the filesystem freeze that runs at the start of every backup. This filesystem freeze deadlock usually happens on a VPS that uses loop-mounted image files, in-guest Internet Small Computer Systems Interface (iSCSI) storage such as Longhorn, Network File System (NFS) or Filesystem in Userspace (FUSE) mounts, or cPanel’s secure /tmp. Stop the deadlock by blocking the freeze commands in the QEMU guest agent configuration on your VPS. The trade-off is that backups no longer pause disk writes, so databases may need to recover when you restore a backup.
Symptoms of a Hostinger VPS freezing during backups
A Hostinger VPS affected by a filesystem freeze deadlock stops responding during a scheduled backup and recovers only after a reboot. There are three signs to check:
- The VPS becomes unreachable at the same time as a backup listed in Snapshots & Backups.
- The VPS stays unresponsive after the backup ends and only comes back when you restart it.
- The system journal from the frozen session ends with the line
guest-fsfreeze called.
Common causes of filesystem freeze deadlocks on a Hostinger VPS
A filesystem freeze deadlocks when one filesystem on the VPS writes its data through another filesystem that is already frozen. The QEMU guest agent waits for the first filesystem to freeze, the first filesystem waits for the second one, and neither can continue.
There are five common setups that cause a filesystem freeze deadlock on a Hostinger VPS:
|
Setup |
Example |
How to check |
|
Loop-mounted image file |
An ext4 image file stored on |
|
|
In-guest iSCSI storage |
Longhorn or open-iscsi running inside the VPS. |
|
|
NFS mounts |
A network share mounted inside the VPS. |
|
|
FUSE mounts |
sshfs, rclone mount, or s3fs. |
|
|
cPanel secure |
The |
See the cPanel installations on a Hostinger VPS section of this article. |
A setup is a likely cause of the freeze if its command returns a result.
cPanel installations on a Hostinger VPS
On a manually installed cPanel, the securetmp feature can block the filesystem freeze. Remove securetmp by following How to fix cPanel freeze on backup creation at Hostinger. The cPanel securetmp fix keeps filesystem freeze on, so you don’t need to block the freeze commands in the QEMU guest agent.
Turn off filesystem freeze on a Hostinger VPS with the QEMU guest agent
Turn off filesystem freeze for your Hostinger VPS backups by blocking the freeze commands in the QEMU guest agent configuration. Blocking the freeze commands needs root access to your VPS over SSH.
- Open the QEMU guest agent configuration file:
sudo nano /etc/qemu/qemu-ga.conf - Add these lines to the file. Add only the
block-rpcsline under the existing[general]section if the file already has one:[general] block-rpcs = guest-fsfreeze-freeze,guest-fsfreeze-freeze-list - Save the file and restart the QEMU guest agent:
sudo systemctl restart qemu-guest-agent - Confirm the QEMU guest agent is running:
sudo systemctl status qemu-guest-agent
The next Hostinger VPS backup runs without freezing the filesystems. Turn filesystem freeze back on by removing the block-rpcs line and restarting the QEMU guest agent.
What changes when filesystem freeze is off for Hostinger VPS backups
With filesystem freeze off, a Hostinger VPS backup captures the disk while applications are still writing to it. The restored copy looks like a server that lost power at the moment of the backup.
Journaling filesystems such as ext4, and databases such as MySQL and PostgreSQL, usually recover from this power-loss state on their next start. Writes that were in progress during the backup can be missing from the restored copy.
Schedule a database dump shortly before your backup time so the backup contains a consistent copy of each database. For example, run mysqldump or pg_dump in a cron job.
Keep filesystem freeze on if your VPS doesn’t freeze during backups. Filesystem freeze gives you more reliable restores for databases and other write-heavy applications.
Blocking the freeze commands in the QEMU guest agent keeps a Hostinger VPS with loop mounts, in-guest iSCSI, NFS, or FUSE storage online during backups. You can undo the change at any time.
NOTES
- Repeat the change after a reinstall, because reinstalling the operating system replaces
/etc/qemu/qemu-ga.conf.
Hostinger VPS filesystem freeze FAQ
Will turning off filesystem freeze stop my VPS backups?
No. Hostinger VPS backups keep running on the same schedule after you turn off filesystem freeze. The backups are taken without pausing disk writes first.
Does turning off filesystem freeze affect snapshots?
Yes. Blocking the freeze commands in the QEMU guest agent stops the filesystem freeze for both backups and snapshots, because the QEMU guest agent rejects every freeze request.
Do I need to contact support to turn off filesystem freeze?
No. You can turn off filesystem freeze yourself by editing the QEMU guest agent configuration on your Hostinger VPS.
Additional resources