From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 32F041FF138 for ; Wed, 18 Mar 2026 22:40:25 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 63FFAB3FB; Wed, 18 Mar 2026 22:40:17 +0100 (CET) From: Marco Gaiarin Subject: Re: Replication error: dataset is busy Date: Wed, 18 Mar 2026 13:43:50 +0100 Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!! Message-ID: <49jq8m-8ul1.ln1@leia.lilliput.linux.it> References: X-Trace: eraldo.lilliput.linux.it 1773868715 3270039 192.168.1.45 (18 Mar 2026 21:18:35 GMT) To: Marco Gaiarin X-Mailer: tin/2.6.4-20240224 ("Banff") (Linux/6.17.0-19-generic (x86_64)) X-Gateway-System: SmartGate 1.4.5 In-Reply-To: ; from SmartGate on Wed, Mar 18, 2026 at 22:36:01PM +0100 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.428 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DATE_IN_PAST_06_12 1.543 Date: is 6 to 12 hours before Received: date 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 SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: UR3P24QELK4ARZBV2BV6S4WU6YVCS7PC X-Message-ID-Hash: UR3P24QELK4ARZBV2BV6S4WU6YVCS7PC 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 CC: pve-user@lists.proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE user list List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > It is clear that somethink remains 'locked' on the non-rebooted node > (cnpve1), but how identify and unlock them? ...for a sake of completeness, i was forced to reboot the node to solve this; because VM was non-migreable, i was forced to reboot VM too. FYI. --