digint / digint/btrbk

use two different lock files

Open
#331 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Perl
Stars
2.1k
Forks
139
PR merge metrics
No merged PRs in 30d

Description

hi

i think it would be better to use two different lock files
one for the snapshot state
and a second one for the transfer-to-target state

reason:
if you add a new target and you are running hourly btrbk it can happen
that the transfer is still ongoing and no new hourly snapshots are created
during this timewindow.

with two lock files the second instance of btrbk would only do the snapshoting
and after all old transfers are done the new snapshots would be moved
automatically later

thanks!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.