OpenBSD - guest fsfreeze - command not found

Jul 11, 2023
32
15
13
Hi,

i've upgraded a set of older systems to the lastest PVE/PBS versions and since then, PBS shows the following error during backup

Code:
ERROR: unable to freeze guest fs - The command guest-fsfreeze-freeze has not been found

It sums up to a WARNING: 14 at the end of every run (for every OpenBSD machine a warning), but at least if successfully finishes.
According to the message a freeze of the OS file system doesn't work anymore.

The machines affected are running OpenBSD (latest version) and also the command qm guest cmd 122 info
doesn't show any command like fsfreeze-freeze anymore.

I'm using the qemu package on all machines and 'serial' as connection method within the config. That's how it worked all the
years. Before the upgrade the messages looked like this:

Code:
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task abc

Is the problem now on PBS (new command, not reverse compatible) or OpenBSD (missing new command) side?

Thanks, Mark
 
Hi @Chris ,

i've seen that thread before and also i can see, that the backup successfully finishes, so it throws an ERROR, but summarizes to a WARNING at the end. My question as stated in the previous post is "what and where did the changes come from, that lead to that problem?" Is PBS using a new command, which OpenBSD doesn't support, but is missing at least a fallback solution to support the old command? As written before ...fsfreeze seamed to have worked fine. I'd like to have more details and perhaps we can support sth for virtio(4) on OpenBSD.
 
Last edited:
My question as stated in the previous post is "what and where did the changes come from, that lead to that problem?
As stated in the other thread, the logging behavior was changed, so the fsfreeze command might never have worked, but just was not logged as such. Please post the output analog to the one requested in the other thread, or chim in there to not duplicate threads.
Is PBS using a new command, which OpenBSD doesn't support, but missed to at least have a fallback?
No, PBS did not change anything here, this is rather most likely caused by the changes in logging on PVE/vzdump side.
 
Ok, thanks, @chris. Let's move over to that thread.