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 AD2E590973 for ; Mon, 12 Feb 2024 13:28:06 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8F37118938 for ; Mon, 12 Feb 2024 13:27:36 +0100 (CET) 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 ; Mon, 12 Feb 2024 13:27:35 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 49A18479B5 for ; Mon, 12 Feb 2024 13:27:35 +0100 (CET) From: Dominik Csapak To: pbs-devel@lists.proxmox.com Date: Mon, 12 Feb 2024 13:27:34 +0100 Message-Id: <20240212122734.1991317-1-d.csapak@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.020 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 T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pbs-devel] [PATCH proxmox-backup v2] fix #5229: tape: remove max sequence number limit 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: Mon, 12 Feb 2024 12:28:06 -0000 The idea was to limit the number of tapes in a media set, but this was not enforced when adding a medium to a media set, only on read/parsing the inventory. With that, it is possible to create media sets greater than the limit which in turn blocks access to most functions via api/cli/gui due to the check. Instead of enforcing an arbitrary limit, simply warn on creation when the media-set is very large (20). To restore the whole media set, the time taken would still be at least 38 hours for LTO-4 and 250 hours for LTO-9. We already have a section in the docs where we tell about the disadvantages of large media sets. Signed-off-by: Dominik Csapak --- changes from v1: * better sentence in commit message about restore time * keep the limit as a constant (but with a different name, at different location) src/tape/media_set.rs | 10 ---------- src/tape/pool_writer/mod.rs | 12 ++++++++++++ 2 files changed, 12 insertions(+), 10 deletions(-) diff --git a/src/tape/media_set.rs b/src/tape/media_set.rs index 8c08efd9..894c8ae3 100644 --- a/src/tape/media_set.rs +++ b/src/tape/media_set.rs @@ -13,8 +13,6 @@ pub struct MediaSet { } impl MediaSet { - pub const MEDIA_SET_MAX_SEQ_NR: u64 = 100; - #[allow(clippy::new_without_default)] pub fn new() -> Self { let uuid = Uuid::generate(); @@ -41,14 +39,6 @@ impl MediaSet { } pub fn insert_media(&mut self, uuid: Uuid, seq_nr: u64) -> Result<(), Error> { - if seq_nr > Self::MEDIA_SET_MAX_SEQ_NR { - bail!( - "media set sequence number to large in media set {} ({} > {})", - self.uuid.to_string(), - seq_nr, - Self::MEDIA_SET_MAX_SEQ_NR - ); - } let seq_nr = seq_nr as usize; if self.media_list.len() > seq_nr { if self.media_list[seq_nr].is_some() { diff --git a/src/tape/pool_writer/mod.rs b/src/tape/pool_writer/mod.rs index f1224bdd..a6ba4a1d 100644 --- a/src/tape/pool_writer/mod.rs +++ b/src/tape/pool_writer/mod.rs @@ -32,6 +32,10 @@ use super::file_formats::{ PROXMOX_BACKUP_CATALOG_ARCHIVE_MAGIC_1_0, PROXMOX_BACKUP_CATALOG_ARCHIVE_MAGIC_1_1, }; +// Warn when the sequence number reaches this limit, as large +// media sets are error prone and take a very long time to restore from. +const MEDIA_SET_SEQ_NR_WARN_LIMIT: u64 = 20; + struct PoolWriterState { drive: Box, // Media Uuid from loaded media @@ -272,6 +276,14 @@ impl PoolWriter { let media_set = media.media_set_label().unwrap(); + if is_new_media && media_set.seq_nr >= MEDIA_SET_SEQ_NR_WARN_LIMIT { + task_warn!( + worker, + "large media-set detected ({}), consider using a different allocation policy", + media_set.seq_nr + ); + } + drive.assert_encryption_mode(media_set.encryption_key_fingerprint.is_some())?; self.status = Some(PoolWriterState { -- 2.30.2