@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
2727.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
2828.in \\n[ rst2man-indent\\n[ rst2man-indent-level ] ]u
2929..
30- .TH "BORG-CHECK" 1 "2024-11-16 " "" "borg backup tool"
30+ .TH "BORG-CHECK" "1" "2025-04-21 " "" "borg backup tool"
3131.SH NAME
3232borg-check \- Check repository consistency
3333.SH SYNOPSIS
@@ -44,7 +44,7 @@ the file magic headers, and both the metadata and data of all objects in
4444the repository. The read data is checked by size and hash. Bit rot and other
4545types of accidental damage can be detected this way. Running the repository
4646check can be split into multiple partial checks using \fB \-\- max \- duration \fP \& .
47- When checking a \fI \% ssh:// \fP remote repository, please note that the checks run on
47+ When checking a < ssh://> remote repository, please note that the checks run on
4848the server and do not cause significant network traffic.
4949.IP 2. 3
5050Checking consistency and correctness of the archive metadata and optionally
@@ -137,37 +137,16 @@ objects from the repository after it did a 2nd try to read them correctly.
137137.IP 2. 3
138138When checking the consistency and correctness of archives, repair mode might
139139remove whole archives from the manifest if their archive metadata chunk is
140- corrupt or lost. On a chunk level (i.e. the contents of files), repair mode
141- will replace corrupt or lost chunks with a same\- size replacement chunk of
142- zeroes. If a previously zeroed chunk reappears, repair mode will restore
143- this lost chunk using the new chunk.
140+ corrupt or lost. Borg will also report files that reference missing chunks.
144141.UNINDENT
145142.sp
146- Most steps taken by repair mode have a one\- time effect on the repository, like
147- removing a lost archive from the repository. However, replacing a corrupt or
148- lost chunk with an all\- zero replacement will have an ongoing effect on the
149- repository: When attempting to extract a file referencing an all\- zero chunk,
150- the \fB extract \fP command will distinctly warn about it. The FUSE filesystem
151- created by the \fB mount \fP command will reject reading such a \(dq zero\- patched\(dq
152- file unless a special mount option is given.
153- .sp
154- As mentioned earlier, Borg might be able to \(dq heal\(dq a \(dq zero\- patched\(dq file in
155- repair mode, if all its previously lost chunks reappear (e.g. via a later
156- backup). This is achieved by Borg not only keeping track of the all\- zero
157- replacement chunks, but also by keeping metadata about the lost chunks. In
158- repair mode Borg will check whether a previously lost chunk reappeared and will
159- replace the all\- zero replacement chunk by the reappeared chunk. If all lost
160- chunks of a \(dq zero\- patched\(dq file reappear, this effectively \(dq heals\(dq the file.
161- Consequently, if lost chunks were repaired earlier, it is advised to run
162- \fB \-\- repair \fP a second time after creating some new backups.
163- .sp
164143If \fB \-\- repair \-\- find \- lost \- archives \fP is given, previously lost entries will
165144be recreated in the archive directory. This is only possible before
166145\fB borg compact \fP would remove the archives\(aq data completely.
167146.SH OPTIONS
168147.sp
169148See \fI borg \- common(1) \fP for common options of Borg commands.
170- .SS optional arguments
149+ .SS options
171150.INDENT 0.0
172151.TP
173152.B \-\- repository\- only
0 commit comments