Mention .partial objects in the help and config init text
prune --help, remote info --help, the snapshot create --prune flag, the config init template's prune_grace_period comment and the runPostBackupPrune comment each listed what prune deletes or remote info counts, and none named the .partial objects this change adds. They do now; the --prune flag refers to prune instead of repeating its list. Model: opus-5-5
This commit is contained in:
1 parent
332c2d30a2
commit
92296daf52
5 files changed
+22
-19
No files matched your search
@@ -269,9 +269,11 @@ storage_url: ""
|
||||
|
||||
# How old a blob that no snapshot lists must be before prune deletes it,
|
||||
# and how old every object in a directory under metadata/ with no manifest
|
||||
# must be before prune deletes that directory. A backup uploads its blobs
|
||||
# and its db.zst.age before its manifest, so on a destination shared
|
||||
# between hosts or users this must be longer than the longest backup run.
|
||||
# must be before prune deletes that directory. prune also deletes a
|
||||
# .partial object left by a killed upload only once it is this old. A
|
||||
# backup uploads its blobs and its db.zst.age before its manifest, so on
|
||||
# a destination shared between hosts or users this must be longer than
|
||||
# the longest backup run.
|
||||
# It does not protect a blob a backup reuses from an earlier run that
|
||||
# stopped before its manifest: that blob keeps the time of its first
|
||||
# upload, so a prune can delete it.
|
||||
|
||||
Reference in new issue
Block a user