From d5eb7abbffe467bebef3f59831333d8c73349e3a Mon Sep 17 00:00:00 2001 From: Dillard Blom Date: Fri, 6 Nov 2026 12:02:38 +0100 Subject: [PATCH] Guide: after a full disk, run the restore again as in step 8 --- docs/DISASTER-RECOVERY.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/DISASTER-RECOVERY.md b/docs/DISASTER-RECOVERY.md index eedf155..cd517b6 100644 --- a/docs/DISASTER-RECOVERY.md +++ b/docs/DISASTER-RECOVERY.md @@ -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,