From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pbs-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id E08E91FF162 for <inbox@lore.proxmox.com>; Sat, 5 Apr 2025 11:05:33 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5CDCFB135; Sat, 5 Apr 2025 11:05:31 +0200 (CEST) From: Christian Ebner <c.ebner@proxmox.com> To: pbs-devel@lists.proxmox.com Date: Sat, 5 Apr 2025 11:05:09 +0200 Message-Id: <20250405090512.165609-7-c.ebner@proxmox.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250405090512.165609-1-c.ebner@proxmox.com> References: <20250405090512.165609-1-c.ebner@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.030 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: [pbs-devel] [PATCH v9 proxmox-backup 6/9] docs: mention GC atime update check for tuning options X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion <pbs-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pbs-devel/> List-Post: <mailto:pbs-devel@lists.proxmox.com> List-Help: <mailto:pbs-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox Backup Server development discussion <pbs-devel@lists.proxmox.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" <pbs-devel-bounces@lists.proxmox.com> Document the gc-atime-safety-check flag and describe the behavior it controls, by adding it as additional bullet point to the documented datastore tuning options. This also fixes the intendation for the cli example how to set the sync level, to make it clear that still belongs to the previous bullet point. Signed-off-by: Christian Ebner <c.ebner@proxmox.com> --- changes since version 8: - fixed outdated commit message docs/storage.rst | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/storage.rst b/docs/storage.rst index 490302955..db61ca58f 100644 --- a/docs/storage.rst +++ b/docs/storage.rst @@ -435,9 +435,16 @@ There are some tuning related options for the datastore that are more advanced: This can be set with: -.. code-block:: console + .. code-block:: console + + # proxmox-backup-manager datastore update <storename> --tuning 'sync-level=filesystem' - # proxmox-backup-manager datastore update <storename> --tuning 'sync-level=filesystem' +* ``gc-atime-safety-check``: Datastore GC atime update safety check: + You can explicitly `enable` or `disable` the atime update safety check + performed on datastore creation and garbage collection. This checks if atime + updates are handled as expected by garbage collection and therefore avoids the + risk of data loss by unexpected filesystem behavior. It is recommended to set + this to enabled, which is also the default value. If you want to set multiple tuning options simultaneously, you can separate them with a comma, like this: -- 2.39.5 _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel