From e00ffabd10cd20130dd96d710595ea3e30a929a8 Mon Sep 17 00:00:00 2001 From: viq Date: Sun, 2 Aug 2020 21:05:47 +0200 Subject: [PATCH] Better description of how cache and rebuilds of it work and how the workaround applies to that --- docs/faq.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/faq.rst b/docs/faq.rst index 44caf23de..1fcae6ecc 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -734,6 +734,17 @@ connections and release the lock). The borg cache eats way too much disk space, what can I do? ----------------------------------------------------------- +This may especially happen if borg needs to rebuild the local "chunks" index - +either because it was removed, or because it was not coherent with the +repository state any more (e.g. because another borg instance changed the +repository). + +To optimize this rebuild process, borg caches per-archive information in the +``chunks.archive.d/`` directory. It won't help the first time it happens, but it +will make the subsequent rebuilds faster (because it needs to transfer less data +from the repository). While being faster, the cache needs quite some disk space, +which might be unwanted. + There is a temporary (but maybe long lived) hack to avoid using lots of disk space for chunks.archive.d (see :issue:`235` for details):