Progress of `Remote: checking segment file /whatever/data/17/17078...`
- Dominant language
- Python
- Stars
- 13.7k
- Forks
- 875
- Avg merge
- 11h 15m
- Merged PRs (30d)
- 192
Description
## Have you checked borgbackup docs, FAQ, and open GitHub issues?
Did not found anything; but I did not check in borg 2.0.
## Is this a BUG / ISSUE report or a QUESTION?
Feature request. And really just a minor comfort feature.
## System information. For client/server mode post info for both machines.
#### Your borg version (borg -V).
IIRC remote is borg 1.2.4 (Hetzner StorageBox).
#### Full borg commandline that lead to the problem (leave away excludes and passwords)
`borg check --repair --debug`
## Describe the problem you're observing.
`borg check --repair --debug` prints:
```
[...]
Remote: checking segment file /whatever/data/17/17078...
[...]
```
and
```
[...]
Remote: compacting segment 4319 with usage count 3 (maybe freeable: 98.88% [100498350 bytes])
[...]
```
I therefore know which segment borg is checking or compacting right now, but I do not know how many are still to go. (i.e. should I grab a coffee or should I go to bed? 😀).
borg already prints this once at the beginning, but it is very likely that the terminal scroll buffer is too small to being able to scroll all the way up 😅:
```
Remote: Segment transaction is 18594
Remote: Determined transaction is 18594
Remote: Found 4314 segments
```
While analyzing archives, there is such a count:
```
[...]
Analyzing archive a5a5b138021d-2023-10-31T23:01:07.973430 (2/61)
[...] ^^^^
```
This is really just a minor feature request. It might still be nice to know about the progress, so one can estimate whether the operation is taking some more minutes or some more hours :)
Related: `borg info` (maybe only `--json`) could also print something like `segments_count` and `max_segment_index` -- but that is probably only useful for some very special use cases.
Contributor guide
Assessment
This issue has not been assessed yet.