Guide: after a full disk, run the restore again as in step 8

2026-11-06 12:02:38 +01:00
parent 4c973d5cd8
commit d5eb7abbff
1 changed files with 2 additions and 2 deletions
@@ -125,8 +125,8 @@ without `--install-apps`:
 - Files that cannot be read are left out and listed at the end; everything else is restored.
 - **Check the disk first if the reason is "Size mismatch".** In this version a full disk looks like
  damaged data: the message then points at `--salvage`, and with `--salvage` the restore goes on and
-  lists the remaining files. The backup itself is fine: make room and run the same command again
-  with `--force`. To be fixed in 1.0.3.
+  lists the remaining files. The backup itself is fine: make room and run the restore again as in
+  step 8, without `--salvage` unless the backup is damaged as well. To be fixed in 1.0.3.
 - If the database cannot be restored (its dump is damaged, or it does not fit this
  installation), the database stays as the fresh installation made it, and the data directory
  and config of the backup go to a folder of their own in the data directory,