From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id A55BB6020C for ; Fri, 16 Oct 2020 09:37:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 93D0B18412 for ; Fri, 16 Oct 2020 09:37:23 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 2CCE918404 for ; Fri, 16 Oct 2020 09:37:23 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id EC2A145DA7 for ; Fri, 16 Oct 2020 09:37:22 +0200 (CEST) Date: Fri, 16 Oct 2020 09:37:06 +0200 (CEST) From: Dietmar Maurer To: Proxmox Backup Server development discussion , Stefan Reiter Message-ID: <1315397434.282.1602833826242@webmail.proxmox.com> In-Reply-To: <1528426253.279.1602830035538@webmail.proxmox.com> References: <20201015104916.21170-1-s.reiter@proxmox.com> <20201015104916.21170-3-s.reiter@proxmox.com> <1528426253.279.1602830035538@webmail.proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.4-Rev11 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.064 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pbs-devel] [PATCH v2 proxmox-backup 2/4] datastore: add manifest locking X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2020 07:37:53 -0000 > > - let _guard; > > + let (_guard, _manifest_guard); > > if !force { > > _guard = lock_dir_noblock(&full_path, "snapshot", "possibly running or in use")?; > > + _manifest_guard = self.lock_manifest(backup_dir); > > I think this is unnecessary. An update manifest should not block a remove_backup_dir. > What for exactly? Ok, Fabian just told be that this is required to avoid unexpected error messages, so I will apply this now.