From 16e4b308703237ad608749df38f1916f49796a92 Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Mon, 30 Dec 2024 22:40:15 +0100 Subject: [PATCH 1/2] binary readme: first check faq and existing issues --- docs/binaries/00_README.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/binaries/00_README.txt b/docs/binaries/00_README.txt index ea5d80cdc1..4a9e104a93 100644 --- a/docs/binaries/00_README.txt +++ b/docs/binaries/00_README.txt @@ -69,7 +69,10 @@ platforms). Reporting issues ---------------- -If you find issues, please open a ticket on our issue tracker: + +Please first check the FAQ and whether a github issue already exists. + +If you find a NEW issue, please open a ticket on our issue tracker: https://github.com/borgbackup/borg/issues/ From cda01c7ba5a36e267afadd7b4e6b2f33b7164de8 Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Mon, 30 Dec 2024 22:58:31 +0100 Subject: [PATCH 2/2] docs: add FAQ entry about pure-python msgpack warning, fixes #8323 --- docs/faq.rst | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/faq.rst b/docs/faq.rst index e52aa74cc6..c944430dc2 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -1035,6 +1035,32 @@ A workaround is to set the option ``--files-cache=ctime,size`` to exclude the in number comparison from the files cache check so that files with different inode numbers won't be treated as modified. +Using a pure-python msgpack! This will result in lower performance. +------------------------------------------------------------------- + +borg uses `msgpack` to serialize/deserialize data. + +`msgpack` has 2 implementations: + +- a fast one (C code compiled into a platform specific binary), and +- a slow pure-python one. + +The slow one is used if it can't successfully import the fast one. + +If you use the pyinstaller-made borg "fat binary" which we offer on github +releases, it could be that you downloaded a binary that does not match the +(g)libc on your system. + +Binaries made for an older glibc than the one you have on your system usually +just work, but the opposite is not necessarily the case and can lead to misc. +issues - like failing to load the fast msgpack code or not working at all. + +So: try a binary made for an older glibc. + +If you see this without using a "fat binary" from us, it usually means that +msgpack is not built / installed correctly. It could be also that the platform +is not fully supported (so the python code works, but there is no fast binary +code). Is there a way to limit bandwidth with Borg? --------------------------------------------