Skip to content

incremental repo check#4422

Merged
ThomasWaldmann merged 3 commits intoborgbackup:masterfrom
ThomasWaldmann:incremental-repo-check
Mar 10, 2019
Merged

incremental repo check#4422
ThomasWaldmann merged 3 commits intoborgbackup:masterfrom
ThomasWaldmann:incremental-repo-check

Conversation

@ThomasWaldmann
Copy link
Member

fixes #1657.

@ThomasWaldmann ThomasWaldmann force-pushed the incremental-repo-check branch from 4a70759 to 913c2d1 Compare March 4, 2019 21:02
@codecov-io
Copy link

codecov-io commented Mar 4, 2019

Codecov Report

Merging #4422 into master will decrease coverage by 0.16%.
The diff coverage is 61.29%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4422      +/-   ##
==========================================
- Coverage   84.24%   84.08%   -0.17%     
==========================================
  Files          37       37              
  Lines        9509     9538      +29     
  Branches     1582     1589       +7     
==========================================
+ Hits         8011     8020       +9     
- Misses       1049     1061      +12     
- Partials      449      457       +8
Impacted Files Coverage Δ
src/borg/remote.py 79.37% <100%> (ø) ⬆️
src/borg/archiver.py 81.61% <25%> (-0.26%) ⬇️
src/borg/repository.py 84.58% <65.38%> (-0.85%) ⬇️
src/borg/archive.py 83.45% <0%> (-0.22%) ⬇️
src/borg/helpers/parseformat.py 89.19% <0%> (+0.17%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 42ea069...4858030. Read the comment docs.

@textshell
Copy link
Member

From a short look this looks good.

I'd prefer not to write to config for non critical operations. But that would complicate the code a lot. But if users are going to check a repo there might actually be some storage breakage which this could make even worse. (one way to do that would be to have an auxiliary file that is like config and that stores all keys outside of a manually maintained critical set)

@ThomasWaldmann
Copy link
Member Author

True.

But otoh the only really critical thing in the config is the key (in repokey modes) and we advise to have a key backup.

Also, the config is not directly overwritten, but first written to a tmp name and then renamed over the previous config (plus some syncs).

@textshell
Copy link
Member

Yes they are both true. But i think i explicitly ruled out using config for nounce because i wanted to avoid having frequently changing information in config.

And yes, that key is primarily what we want to protect. And maybe the structure so borg still recognizes the directory are repo.

@ThomasWaldmann ThomasWaldmann changed the title WIP: incremental repo check incremental repo check Mar 10, 2019
@ThomasWaldmann
Copy link
Member Author

I'm merging this as is now and will open a ticket about separating config into 2.

@ThomasWaldmann ThomasWaldmann merged commit d493806 into borgbackup:master Mar 10, 2019
@ThomasWaldmann ThomasWaldmann deleted the incremental-repo-check branch March 10, 2019 19:21
@ThomasWaldmann
Copy link
Member Author

see #4428.

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

Successfully merging this pull request may close these issues.

Incremental repository check

3 participants