-
-
Notifications
You must be signed in to change notification settings - Fork 743
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add warnings on repository copies to avoid future problem like #4272 #4285
Conversation
docs/faq.rst
Outdated
| repository, because Borg is cautious and does not automatically remove | ||
| stale locks made by a different host. | ||
| Yes, you could just copy all the files. But you generally do not want | ||
| to do that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, that is maybe a bit too restrictive.
quite some people e.g. use rclone to have a copy of their local repo in the cloud, just in case their house burns down or so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how should i phrase this instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should mention borg with-lock ... here. it will also produce a lock, but it will use the lock so not other borg updates the repo while it is copied / synchronized.
the problem is not making the copy, but using borg to access more than 1 of the set of original and cloned repos (includes: just reading, updating independently, etc.).
|
@anarcat i improved it myself, have a look. i chose to refactor it a bit, to make the point more clearer:
|
|
also changed "repo2" to "copy-of-repo" to avoid people having the impression that this creates another usable repository. |
|
I'll merge it as is, hopefully it is ok for you @anarcat. Want to get 1.1.9 out tonight. |
|
thanks for taking this the final steps... :) |
fixes #3933.