Guide: after a full disk, run the restore again as in step 8
CI / unit (8.2) (push) Has been cancelled
CI / unit (8.3) (push) Has been cancelled
CI / unit (8.4) (push) Has been cancelled
CI / psalm (push) Has been cancelled
CI / frontend (push) Has been cancelled
CI / integration (mariadb, 32) (push) Has been cancelled
CI / integration (mariadb, 33) (push) Has been cancelled
CI / integration (mariadb, 34) (push) Has been cancelled
CI / integration (mariadb, 35) (push) Has been cancelled
CI / integration (pgsql, 32) (push) Has been cancelled
CI / integration (pgsql, 33) (push) Has been cancelled
CI / integration (pgsql, 34) (push) Has been cancelled
CI / integration (pgsql, 35) (push) Has been cancelled
CI / integration (sqlite, 32) (push) Has been cancelled
CI / integration (sqlite, 33) (push) Has been cancelled
CI / integration (sqlite, 34) (push) Has been cancelled
CI / integration (sqlite, 35) (push) Has been cancelled
CI / integration-targets (push) Has been cancelled
CI / integration-user (32) (push) Has been cancelled
CI / integration-user (33) (push) Has been cancelled
CI / integration-user (34) (push) Has been cancelled
CI / integration-user (35) (push) Has been cancelled
CI / integration-full-restore (push) Has been cancelled

This commit is contained in:
2026-11-06 12:02:38 +01:00
parent 4c973d5cd8
commit d5eb7abbff
+2 -2
View File
@@ -125,8 +125,8 @@ without `--install-apps`:
- Files that cannot be read are left out and listed at the end; everything else is restored. - 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 - **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 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 lists the remaining files. The backup itself is fine: make room and run the restore again as in
with `--force`. To be fixed in 1.0.3. 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 - 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 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, and config of the backup go to a folder of their own in the data directory,