From c6a87e340c1df818c9df5e3da37d6b926c5f8052 Mon Sep 17 00:00:00 2001 From: Christian Ebner Date: Sat, 5 Apr 2025 11:05:09 +0200 Subject: [PATCH] docs: mention GC atime update check for tuning options 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 --- docs/storage.rst | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/storage.rst b/docs/storage.rst index 49030295..db61ca58 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 --tuning 'sync-level=filesystem' + # proxmox-backup-manager datastore update --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: