From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 462F11FF0A7 for ; Wed, 16 Sep 2026 15:00:57 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 1663021572; Wed, 16 Sep 2026 15:00:28 +0200 (CEST) Date: Wed, 16 Sep 2026 14:57:14 +0200 From: Marco Gaiarin To: pve-user@lists.proxmox.com Subject: Re: Two nodes asymmetrical cluster, backup, stall of one node. Message-ID: References: <20260901105522.Horde.vgrn9fzQ416tczxJi0dVq0Y@drive.antreich.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260901105522.Horde.vgrn9fzQ416tczxJi0dVq0Y@drive.antreich.com> Organization: Casa Gaiarin User-Agent: Mutt/2.2.12 (2023-09-09) X-SPAM-LEVEL: Spam detection results: 0 DMARC_PASS -0.1 DMARC pass policy JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 65DDNSJTIG4DM7MIZE7A2DZDJ2GNFQ5F X-Message-ID-Hash: 65DDNSJTIG4DM7MIZE7A2DZDJ2GNFQ5F X-MailFrom: gaio@lilliput.linux.it X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE user list List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Mandi! Alwin Antreich In chel di` si favelave... Sorry for the late answer, i was busy on other things... > > i've trid to kill it, even with '-9', but whitout success. > Processes in D state can't be killed, only a reboot helps. OK.   > The pvesr is doing a snapshot sync, which is not involving NFS. Are you running two different things, one replication and a vzdump backup at the same time?  Yes, there are replica of other VMs, but not this specific VM under backup. Anyway, yes: on the same note there's a backup and a replica. Effectively when i reboot the node, i receive two errors of failed replicas from the 2 VMs on the other node, that was stalled. > > I can surely setup TWO backup job, but... thanks. > That's the solution. Plus add a bandwidth limit to reduce the IO pressure. I've tried to split backup job and limit (a little) the bandwidth, but problem persist. Now i've tried to change backup mode from snapshot to poweroff: the VM under backup is a 'scratch' one and can be safely rebooted. I come back with more info. Thanks. --