Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upcheck the docs + faq about files cache #5371
Open
Comments
ThomasWaldmann
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Oct 3, 2020
also: give a speed example for unchanged files also: explicitly mention chmod/chown changing ctime also: reformat one paragraph
ThomasWaldmann
added a commit
that referenced
this issue
Oct 6, 2020
docs: how to approach borg speed issues, fixes #5371
|
fixed in 1.1-maint. proofreading and forward porting to master still todo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
there are frequent questions like "why is borg slow for me, considering all my files modified" when the underlying filesystem has issues with:
there are quite some related posts on this issue tracker (also see closed issues) and on the borg mailing list.
the usual way to debug / fix this is using
borg create --list ...to see file status and whether a lot of files are considered modified although they should not be plus using thestatcommand on these files to see why borg considers them changed or has a files cache miss (if not obvious, e.g. due to full path change).fixing the issue is sometimes out of borg scope (e.g. mounting always to same mountpoint, not doing chown/chmod by cron) and sometimes tweaking borg's
--files-cache(e.g. if the source fs does not have stable inode numbers).check our docs (esp. borg create and faq) and make them more complete / better discoverable, so less people ask these questions.