Re: [pbs-devel] [PATCH v8 proxmox-backup 6/9] docs: mention GC atime update check for tuning options

["Max Carrara" <m.carrara@proxmox.com>]

On Fri Mar 21, 2025 at 9:02 AM CET, Christian Ebner wrote:
> Document the gc-atime-check flag and describe the behavior it

Small thing: s/gc-atime-check/gc-atime-safety-check ;)

> 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 7:
> - no changes
>
>  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:



_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel