summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorThomas Waldmann <tw@waldmann-edv.de>2022-04-20 00:22:07 +0200
committerThomas Waldmann <tw@waldmann-edv.de>2022-04-20 13:00:34 +0200
commit56262b57bdad7407e7b85d55bcf4f023ed72da5c (patch)
tree10d303d7348a4aba9b786476afec47138896a7ee /docs
parent55f9028611bad2db1a5eb1fcd98b74f7c7326092 (diff)
FAQ: add a hint about --debug-topic=files_cache
Diffstat (limited to 'docs')
-rw-r--r--docs/faq.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/faq.rst b/docs/faq.rst
index 8aa016d8..2c8ff66b 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -932,6 +932,8 @@ Then you do the backup and look at the log output:
details and potential issues).
You can use the ``stat`` command on files to manually look at fs metadata to debug if
there is any unexpected change triggering the ``M`` status.
+ Also, the ``--debug-topic=files_cache`` option of ``borg create`` provides a lot of debug
+ output helping to analyse why the files cache does not give its expected high performance.
When borg runs inside a virtual machine, there are some more things to look at: