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 03E4E6723A for ; Thu, 30 Jul 2020 07:52:02 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DFF2912A8D for ; Thu, 30 Jul 2020 07:51:31 +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)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id C5AFD12A7F for ; Thu, 30 Jul 2020 07:51:30 +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 876B7433EF for ; Thu, 30 Jul 2020 07:51:30 +0200 (CEST) Date: Thu, 30 Jul 2020 07:50:53 +0200 (CEST) From: Dietmar Maurer To: Proxmox Backup Server development discussion , Stefan Reiter Message-ID: <1200038958.55.1596088254348@webmail.proxmox.com> In-Reply-To: <20200729123314.10049-5-s.reiter@proxmox.com> References: <20200729123314.10049-1-s.reiter@proxmox.com> <20200729123314.10049-5-s.reiter@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.3-Rev19 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.088 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 proxmox-backup 4/5] backup: use flock on backup group to forbid multiple backups at once 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: Thu, 30 Jul 2020 05:52:02 -0000 > + // acquire in non-blocking mode, no point in waiting here since other > + // backups could still take a very long time > + tools::lock_file(&mut handle, true, Some(Duration::from_nanos(0))) > + .map_err(|err| { > + match err.downcast_ref::() { > + Some(nix::Error::Sys(nix::errno::Errno::EAGAIN)) => { Honestly, I would remove this special case with downcast - the default error message is good enough. Isn't it? > + return format_err!( > + "unable to acquire lock on backup group {:?} - another backup is already running", > + self.group_path(), > + ); > + }, > + _ => () > + } > + format_err!( > + "unable to acquire lock on backup group {:?} - {}", > + self.group_path(), > + err, > + ) > + })?; > + > + Ok(handle) > + } > +