Docs: a full disk during a restore looks like a damaged backup, to be fixed in 1.0.3

2026-11-06 12:00:52 +01:00
parent b86b07a49c
commit 4c973d5cd8
3 changed files with 10 additions and 0 deletions
@@ -55,6 +55,9 @@ shown under 1.0.0. The git tag of a release candidate goes after the date.

 ### Known issues
 - Empty folders are not backed up or restored; to be fixed in 1.0.3 (#27).
+- A full disk during a restore looks like a damaged backup ("Size mismatch"), and with `--salvage`
+  the restore goes on and lists the remaining files. The backup itself is fine: make room and run
+  the restore again. To be fixed in 1.0.3.

 ## [1.0.1] - 2026-11-01

@@ -296,6 +296,9 @@ On the backlog; know them before you rely on NG Backup:
 - **Empty folders do not come back.** A backup only records files, so a folder without files is
  not restored. To be fixed in 1.0.3
  ([#27](https://github.com/dillardblom/ng_backup/issues/27)).
+- **A full disk during a restore looks like a damaged backup.** The reason shown is "Size mismatch",
+  and with `--salvage` the restore goes on and lists the remaining files. The backup itself is fine:
+  make room and run the restore again. To be fixed in 1.0.3.
 - **Only the data directory is backed up.** Object storage as primary storage (`objectstore` in
  `config.php`) is not supported: a backup refuses to start there. Folders mounted through the
  External storage app are not in the data directory and are **not included**, without a warning.
@@ -123,6 +123,10 @@ without `--install-apps`:
    occ maintenance:mode --off && occ backup:restore:full offsite <snapshot> --salvage --force

 - 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.
 - 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,