..and add more logging when issuing fsfreeze guest commands. The setting takes precedence over freeze-fs-on-backup and deprecates the former.
- At the moment taking a snapshot without RAM does not log whether there was a freeze/thaw, we add logs when issuing freezes/thaws. - The patch does result in an extra log line when making a Backup in snapshot mode. One possible further improvement is to add a message saying that fsfreeze/fsthaw were skipped due to the config when doing snapshots without RAM. Differences from v2: - Print a message on live clones when fsfreeze is skipped due to config - Clean up code a bit - rebase - Fix a typo Differences from v1: - Add setting to enable/disable fsfreeze commands - Change wording in one log message qemu-server: Maximiliano Sandoval (7): add a guest-fsfreeze qga setting block job: mirror: follow guest-fsfreeze setting fix #1964: follow guest-fsfreeze setting on check freeze needed log when issuing a guest-fsfreeze command block job: mirror: reword fsfreeze log entry block job: log if fs-freeze is skipped due to config deprecate freeze-fs-on-backup qga setting src/PVE/QemuConfig.pm | 5 ++++- src/PVE/QemuServer/Agent.pm | 15 ++++++++++++++- src/PVE/QemuServer/BlockJob.pm | 16 ++++++++++++---- src/PVE/VZDump/QemuServer.pm | 7 +++++-- 4 files changed, 35 insertions(+), 8 deletions(-) pve-container: Maximiliano Sandoval (1): log when freezing/thawing filesystem src/PVE/LXC/Config.pm | 2 ++ 1 file changed, 2 insertions(+) qemu-server: Maximiliano Sandoval (1): replication: remove logging when freezing/thawing src/PVE/Replication.pm | 2 -- 1 file changed, 2 deletions(-) Summary over all repositories: 6 files changed, 37 insertions(+), 10 deletions(-) -- Generated by murpp 0.9.0 _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
