-
Notifications
You must be signed in to change notification settings - Fork 78
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
Dealing with duplicity cache lock (.lock file) #8
Comments
I am not really sure how to solve this. The cache is really important for me. I am using backblaze backend backups. This means if i delete the cache then each time i backup i need to build up another cache. This mean additional costs for backups because data is transferred from and to my cloud storage. Maybe we need to make this configurable? |
@blacklabelops Yep, cache is important but (I guess) lockfile (which is orphaned) is not needed on next backup :) |
Im still trying to figure out, how to decide, if a lockfile is really orphaned. |
Added new cleanup script |
@blacklabelops
While I was testing volumerize in a small sized storage, duplicity backup process was interrupt because of storage limitation.
This left .lock file at
/volumerize-cache
directory, which causes the error belowHow about adding a cache-removing script before start backing up?
The text was updated successfully, but these errors were encountered: