From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: "Shannon Sterz" <s.sterz@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH guest-common 0/2] fix #1964: replication config: add a setting to skip freezing guest filesystems
Date: Thu, 22 Oct 2026 12:27:24 +0200 [thread overview]
Message-ID: <s8o33ty58tv.fsf@toolbox> (raw)
In-Reply-To: <DMBAL8CFTODU.BHEE1FTLLPDU@proxmox.com> (Shannon Sterz's message of "Thu, 22 Oct 2026 12:24:30 +0200")
"Shannon Sterz" <s.sterz@proxmox.com> writes:
> On Mon Jul 6, 2026 at 4:03 PM CEST, Maximiliano Sandoval wrote:
>> See the second commit message for more information.
>>
>> We sneak a change removing an unused Data::Dumper import.
>>
>> Tested:
>>
>> - Created a VM with ID 101 in a cluster with nodes pve1 and pve2
>> - Enabled the QGA service inside the guest
>> - Created a replication job with
>>
>> pve2 $ pvesr create-local-job 101-1 pve1 --skip-freeze-fs 1 --schedule '*/1'
>>
>> - Start the VM
>> - Ran: pvesr schedule-now 101-1
>> - cat /var/log/pve/replicate/101-1
>> - checked that it contains the added line in the logs.
>>
>> Then repeated the whole thing without specifying --skip-freeze-fs to ensure
>> nothing was broken.
>>
>> Maximiliano Sandoval (2):
>> replication config: remove unused Data::Dumper
>> fix #1964: replication config: add a setting to skip freezing guest
>> filesystems
>>
>> src/PVE/Replication.pm | 7 +++++++
>> src/PVE/ReplicationConfig.pm | 9 ++++++++-
>> 2 files changed, 15 insertions(+), 1 deletion(-)
>
> seems to work as advertised and the code changes seem to fairly straight
> forward to me. so consider this:
>
> Reviewed-by: Shannon Sterz <s.sterz@proxmox.com>
> Tested-by: Shannon Sterz <s.sterz@proxmox.com>
>
> one small thing i noticed is that if a node does not have the updated
> package, editing the replication job through that node's ui will
> silently drop the new option. however, that is unrelated to this series
> and a more general issue. editing the job on a node with these changes
> keeps the option in place as expected.
Thanks for the feedback. I noticed this morning that "wether" is a typo,
from the Cambridge Dictionary:
wether n.
a male sheep that has been castrated
I suppose that s/wether/whether/ can be done while applying.
This has been requested in the following support cases: #9211193,
#0063246, #5761134, #3261710.
--
Maximiliano
next prev parent reply other threads:[~2026-10-22 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:03 [PATCH guest-common 0/2] fix #1964: replication config: add a setting to skip freezing guest filesystems Maximiliano Sandoval
2026-07-06 14:03 ` [PATCH guest-common 1/2] replication config: remove unused Data::Dumper Maximiliano Sandoval
2026-10-22 11:49 ` applied: " Fiona Ebner
2026-07-06 14:03 ` [PATCH guest-common 2/2] fix #1964: replication config: add a setting to skip freezing guest filesystems Maximiliano Sandoval
2026-10-22 11:55 ` Fiona Ebner
2026-10-22 10:24 ` [PATCH guest-common 0/2] " Shannon Sterz
2026-10-22 10:27 ` Maximiliano Sandoval [this message]
2026-10-22 13:02 ` superseded: " 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=s8o33ty58tv.fsf@toolbox \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@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