upstream/borgbackup
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2026-02-20 00:10:35 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 6

docs: add FAQ entry about pure-python msgpack warning, fixes #8323

Browse source
This commit is contained in:
Thomas Waldmann 2024-12-30 22:58:31 +01:00
parent 16e4b30870
commit cda01c7ba5
No known key found for this signature in database
GPG key ID: 243ACFA951F78E01
1 changed files with 26 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
docs/faq.rst
View file

@ -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?
--------------------------------------------