From 761ff5b2fd6916383578c13c8dce638c19cb4375 Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Wed, 20 Apr 2022 00:22:07 +0200 Subject: [PATCH] FAQ: add a hint about --debug-topic=files_cache --- docs/faq.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/faq.rst b/docs/faq.rst index 96ca36d67..31a75b0e6 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -906,6 +906,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: