Skip to content
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

Closed
darron1217 opened this issue Nov 28, 2017 · 4 comments
Closed

Dealing with duplicity cache lock (.lock file) #8

darron1217 opened this issue Nov 28, 2017 · 4 comments

Comments

@darron1217
Copy link

darron1217 commented Nov 28, 2017

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

Another instance is already running with this archive directory
If you are sure that this is the  only instance running you may delete
the following lockfile and run the command again :
/volumerize-cache/3fe07cc0f71075f95f411fb55ec60120/lockfile.lock

How about adding a cache-removing script before start backing up?

@blacklabelops
Copy link
Owner

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?

@darron1217
Copy link
Author

darron1217 commented Nov 29, 2017

@blacklabelops
I mean removing lockfile.lock instead of removing whole cache
(I actually didn't know the functionality of cache folder...haha)

Yep, cache is important but (I guess) lockfile (which is orphaned) is not needed on next backup :)

@darron1217 darron1217 changed the title Dealing with duplicity cache (.lock file) Dealing with duplicity cache lock (.lock file) Nov 29, 2017
@blacklabelops
Copy link
Owner

Im still trying to figure out, how to decide, if a lockfile is really orphaned.

@blacklabelops
Copy link
Owner

Added new cleanup script cleanCacheLocks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants