From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 4/5] docs: add documentation about the 'sync-level' tuning
Date: Fri, 20 May 2022 14:42:27 +0200 [thread overview]
Message-ID: <20220520124228.3368960-5-d.csapak@proxmox.com> (raw)
In-Reply-To: <20220520124228.3368960-1-d.csapak@proxmox.com>
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
docs/storage.rst | 37 +++++++++++++++++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/docs/storage.rst b/docs/storage.rst
index ab59ad4d..8ca696cd 100644
--- a/docs/storage.rst
+++ b/docs/storage.rst
@@ -338,3 +338,40 @@ and only available on the CLI:
# proxmox-backup-manager datastore update <storename> --tuning 'chunk-order=none'
+* ``sync-level``: Datastore fsync level:
+
+ You can set the level of syncing on the datastore for chunks, which influences
+ the crash resistancy of backups in case of a powerloss or hard shutoff.
+ There are currently three levels:
+
+ - `none` (default): Does not do any syncing when writing chunks. This is fast
+ and normally ok, since the kernel eventually flushes writes onto the disk.
+ The kernel sysctls `dirty_expire_centisecs` and `dirty_writeback_centisecs`
+ are used to tune that behaviour, while the default is to flush old data
+ after ~30s.
+
+ - `filesystem` : This triggers a ``syncfs(2)`` after a backup, but before
+ the task returns `OK`. This way it is ensured that the written backups
+ are on disk. This is a good balance between speed and consistency,.
+ Note that the underlying storage device sitll needs to protect itself against
+ powerloss to flush its internal ephemeral caches to the permanent storage layer.
+
+ - `file` With this mode, a fsync is triggered on every chunk insertion, which
+ makes sure each and every chunk reaches the disk as soon as possible. While
+ this reaches the hightest level of consistency, for many storages (especially
+ slower ones) this comes at the cost of speed. In general the `filesystem`
+ mode is better suited for most setups, but for very fast storages this mode
+ can be ok.
+
+ This can be set with:
+
+.. code-block:: console
+
+ # proxmox-backup-manager datastore update <storename> --tuning 'sync-level=filesystem'
+
+If you want to set multiple tuning options simultaniously, you can seperate them
+with a comma, like this:
+
+.. code-block:: console
+
+ # proxmox-backup-manager datastore update <storename> --tuning 'sync-level=filesystem,chunk-order=none'
--
2.30.2
next prev parent reply other threads:[~2022-05-20 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 12:42 [pbs-devel] [PATCH proxmox-backup 0/5] add 'sync-level' to datatore tuning options Dominik Csapak
2022-05-20 12:42 ` [pbs-devel] [PATCH proxmox-backup 1/5] docs: add information about chunk order option for datastores Dominik Csapak
2022-05-20 12:42 ` [pbs-devel] [PATCH proxmox-backup 2/5] pbs-datastore: chunk_store: use replace_file in insert_chunk Dominik Csapak
2022-05-20 12:42 ` [pbs-devel] [PATCH proxmox-backup 3/5] datastore: implement sync-level tuning for datastores Dominik Csapak
2022-05-23 7:13 ` Fabian Grünbichler
2022-05-24 8:14 ` Thomas Lamprecht
2022-05-20 12:42 ` Dominik Csapak [this message]
2022-05-20 12:42 ` [pbs-devel] [PATCH proxmox-backup 5/5] datastore: make 'filesystem' the default sync-level Dominik Csapak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220520124228.3368960-5-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.