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)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 9DBDD942D3 for ; Wed, 10 Apr 2024 13:18:41 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 866B3DF6D for ; Wed, 10 Apr 2024 13:18:41 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 for ; Wed, 10 Apr 2024 13:18:41 +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 C421E43C9A for ; Wed, 10 Apr 2024 13:18:40 +0200 (CEST) Date: Wed, 10 Apr 2024 13:18:40 +0200 (CEST) From: Dietmar Maurer To: Proxmox Backup Server development discussion , Hannes Laimer Message-ID: <1322089912.5760.1712747920154@webmail.proxmox.com> In-Reply-To: <20240409110012.166472-14-h.laimer@proxmox.com> References: <20240409110012.166472-1-h.laimer@proxmox.com> <20240409110012.166472-14-h.laimer@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.6-Rev61 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.345 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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 v3 13/24] api: mark removable datastores as unplugged after restart 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: Wed, 10 Apr 2024 11:18:41 -0000 > diff --git a/src/bin/proxmox-backup-api.rs b/src/bin/proxmox-backup-api.rs > index e46557a0..50f31d4e 100644 > --- a/src/bin/proxmox-backup-api.rs > +++ b/src/bin/proxmox-backup-api.rs > @@ -10,6 +10,8 @@ use proxmox_lang::try_block; > use proxmox_router::RpcEnvironmentType; > use proxmox_sys::fs::CreateOptions; > > +use pbs_api_types::{DataStoreConfig, MaintenanceMode, MaintenanceType}; > +use pbs_datastore::check_if_available; > use proxmox_rest_server::{daemon, ApiConfig, RestServer}; > > use proxmox_backup::auth_helpers::*; > @@ -73,6 +75,8 @@ async fn run() -> Result<(), Error> { > > proxmox_backup::auth_helpers::setup_auth_context(true); > > + mark_removable_datastores_unplugged()?; Do we really want to fail service startup if that fails? Maybe it is good enough to just log a warning? Or schedule a task to do it at regular intervals?