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:
sneak committed 2026-11-19 07:47:00 +00:00
1 parent 332c2d30a2
commit 92296daf52
5 files changed
+22 -19

No files matched your search

+6 -4
View File
@@ -13,9 +13,10 @@ func NewPruneCommand() *cobra.Command {
cmd := &cobra.Command{
Use: "prune",
Short: "Tidy local database and remote storage",
Long: `Removes orphaned data from the local index database, and
unreferenced blobs and directories under metadata/ with no manifest
from the backup destination store.
Long: `Removes orphaned data from the local index database. From the
backup destination store it removes unreferenced blobs, directories
under metadata/ with no manifest, and .partial objects left by killed
uploads.
Local cleanup drops incomplete snapshots and any files, chunks, or
blobs no longer referenced by a completed snapshot. Remote cleanup
@@ -30,7 +31,8 @@ blob keeps the time of its first upload, so it can be deleted.
Remote cleanup also deletes each directory under metadata/ with no
manifest, as a backup that stopped before its manifest leaves, once
all its objects are older than prune_grace_period and its snapshot is
not in the local index.
not in the local index. It also deletes each .partial object under
metadata/ or blobs/ once it is older than prune_grace_period.
Snapshot create --prune runs the same cleanup automatically; this
command is the manual entry point for the same work (e.g. after a