From: Iztok Gregori <iztok.gregori@elettra.eu>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Unresponsive VM(s) during VZdump
Date: Fri, 10 May 2024 09:36:12 +0200 [thread overview]
Message-ID: <3315b8aa-6ade-4c3f-81e8-812f7db61862@elettra.eu> (raw)
In-Reply-To: <2b94dfec-54d4-4a48-a379-01ef15713da5@elettra.eu>
Hi to all!
On 09/05/24 12:02, Iztok Gregori wrote:
[cut]
>
> In the meantime I found this thread on the forum:
>
> https://forum.proxmox.com/threads/high-io-wait-during-backups-after-upgrading-to-proxmox-7.113790/
>
> which mention the max_workers parameter. I change it to 4 for the next
> scheduled backup and see if there are some improvements (I migrated the
> affected VMs to catch the new configuration).
>
> I will keep you posted!
At the end I've set max_workers parameter to 1 (basically revert it to
PVE 6 default) and the backups didn't cause issues to the guest VMs (or
at least there were no notifications, and the checks I made were all
negative).
Next week, when the upgrade is finished, I will try "fleecing" and I
will revert the max_workers configuration to the default values to see
validate the setup.
Also, in the short term, I'm planning to change the target storage for
vzdump to something more fast.
Have a great day!
Iztok
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2024-05-10 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 8:35 Iztok Gregori
2024-05-09 9:30 ` Mike O'Connor
2024-05-09 10:02 ` Iztok Gregori
2024-05-09 10:11 ` Mike O'Connor
2024-05-09 11:24 ` Alexander Burke via pve-user
[not found] ` <11db3d6f-1879-44b3-9f99-01e6fde6ebc8@alexburke.ca>
2024-05-10 5:21 ` Mike O'Connor
2024-05-10 9:07 ` Fiona Ebner
2024-05-10 7:36 ` Iztok Gregori [this message]
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=3315b8aa-6ade-4c3f-81e8-812f7db61862@elettra.eu \
--to=iztok.gregori@elettra.eu \
--cc=pve-user@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