| 1 |
% bup-validate-ref-links(1) Bup %BUP_VERSION% |
| 2 |
% Rob Browning <[email protected]> |
| 3 |
% %BUP_DATE% |
| 4 |
|
| 5 |
# NAME |
| 6 |
|
| 7 |
bup-validate-ref-links - check repository refs for links to missing objects |
| 8 |
|
| 9 |
# SYNOPSIS |
| 10 |
|
| 11 |
bup validate-ref-links [*ref*...] |
| 12 |
|
| 13 |
# DESCRIPTION |
| 14 |
|
| 15 |
`bup validate-ref-links` checks repository references (e.g. saves) for |
| 16 |
commits or subtrees that refer to missing objects and reports the |
| 17 |
paths to any found. If no *ref*s are provided, checks all refs, |
| 18 |
otherwise only checks those specified. |
| 19 |
|
| 20 |
This command can also be used to validate a save more quickly than |
| 21 |
attempting a `restore` or `join`ing the save to /dev/null, and much |
| 22 |
more quickly for multiple related saves, though it only checks for the |
| 23 |
existence of the leaf (blob) data, it does not attempt to read that |
| 24 |
data. |
| 25 |
|
| 26 |
At the moment, the broken path information is only logged to standard |
| 27 |
error, and is not well specified (i.e. suitable for inspection, but |
| 28 |
not parsing). |
| 29 |
|
| 30 |
Also note that the current implementation may not report all paths to |
| 31 |
a given missing object because it only examines each unique tree or |
| 32 |
commit object once, no matter how often it appears within the refs |
| 33 |
being examined. This means that in order to find every broken save, |
| 34 |
you would need to run the command separately for each ref, which is |
| 35 |
likely to be much more expensive than a combined run because it can't |
| 36 |
skip subtrees that it has encountered before. |
| 37 |
|
| 38 |
# EXIT STATUS |
| 39 |
|
| 40 |
The exit status will be 1 if any broken links are found, 0 if none are |
| 41 |
found, and some other positive integer for other failures. |
| 42 |
|
| 43 |
# SEE ALSO |
| 44 |
|
| 45 |
`bup-fsck`(1), `bup-join`(1), `bup-restore`(1) |
| 46 |
|
| 47 |
# BUP |
| 48 |
|
| 49 |
Part of the `bup`(1) suite. |