public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container/guest-common/qemu-server 0/3] log when freezing or thawing the guest's fs
Date: Mon, 01 Sep 2025 15:03:49 +0200	[thread overview]
Message-ID: <DCHHGLETM8WQ.1L4ISJ6HPXPGV@proxmox.com> (raw)
In-Reply-To: <20250829114337.345358-1-m.sandoval@proxmox.com>

On Fri Aug 29, 2025 at 1:43 PM CEST, Maximiliano Sandoval wrote:
> At the moment taking a snapshot without RAM does not log whether there was a freeze/thaw.
>
> This does not add an extra log line when making a Backup in snapshot mode.
>
> qemu-server:
>
> Maximiliano Sandoval (1):
>   log when issues a guest-fsfreeze command
>
>  src/PVE/QemuConfig.pm | 2 ++
>  1 file changed, 2 insertions(+)
>
>
> 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:
>   3 files changed, 4 insertions(+), 2 deletions(-)

for the vm part this looks fine, the new log lines show up in the log
for a vm's snapshot without ram, but not with ram or backups:

issuing guest-agent 'fs-freeze' command
snapshotting 'drive-scsi0' (vms:vm-100-disk-0)
issuing guest-agent 'fs-thaw' command
TASK OK

for a container this now always says:

freezing guest filesystem
thawing guest filesystem
TASK OK

however, for backups it looks like this:

INFO: starting new backup job: vzdump 101 --remove 0 --mode snapshot --node pve-icon-cleanup --storage local --compress zstd --notification-mode notification-system --notes-template '{{guestname}}'
INFO: Starting Backup of VM 101 (lxc)
INFO: Backup started at 2025-09-01 14:54:33
INFO: status = running
INFO: CT Name: CT101
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
freezing guest filesystem
thawing guest filesystem
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-lxc-101-2025_09_01-14_54_33.tar.zst'
INFO: Total bytes written: 697968640 (666MiB, 215MiB/s)
INFO: archive file size: 201MB
INFO: adding notes to backup
INFO: cleanup temporary 'vzdump' snapshot
INFO: Finished Backup of VM 101 (00:00:03)
INFO: Backup finished at 2025-09-01 14:54:36
INFO: Backup job finished successfully
INFO: notified via target `mail-to-root`
TASK OK

imo it would be nicer to pass down the log function so that it can log
those two lines with the proper log level (`INFO`) here too. however, i
am not sure if that is particularly useful for containers in general. we
don't expose a setting for turning freezing/thawing here to users. the
mechanism is different in my understanding too, as we don't need to rely
on a guest agent for containers anyway. possibly the patch for
pve-container can just be dropped?

other than that:

Tested-by: Shannon Sterz <s.sterz@proxmox.com>
Reviewed-by: Shannon Sterz <s.sterz@proxmox.com>


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-09-01 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 11:43 Maximiliano Sandoval
2025-08-29 11:43 ` [pve-devel] [PATCH qemu-server 1/1] log when issues a guest-fsfreeze command Maximiliano Sandoval
2025-08-29 11:45   ` Maximiliano Sandoval
2025-08-29 11:43 ` [pve-devel] [PATCH container 1/1] log when freezing/thawing filesystem Maximiliano Sandoval
2025-08-29 11:43 ` [pve-devel] [PATCH guest-common 1/1] replication: remove logging when freezing/thawing Maximiliano Sandoval
2025-09-01 13:03 ` Shannon Sterz [this message]
2025-09-02 12:46 ` [pve-devel] superseded: [PATCH container/guest-common/qemu-server 0/3] log when freezing or thawing the guest's fs Maximiliano Sandoval

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DCHHGLETM8WQ.1L4ISJ6HPXPGV@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=pve-devel-bounces@lists.proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal