############ PHASE 4 (redo) — DESTROY the app's live data, for real ############
UTC 2026-08-31T10:01:46Z
NOTE: the first attempt used 'docker volume rm', which docker REFUSED because the stopped
      containers still referenced the volumes. It printed nothing and destroyed nothing.
      An unchecked exit code that looks like success is exactly the trap this drill tests for.

docmost Exited (1) 42 seconds ago
docmost-redis Exited (0) 42 seconds ago
docmost-postgres Exited (0) 29 seconds ago
--- sizes BEFORE the wipe
68989735	/var/lib/docker/volumes/docmost_docmost_postgres_data/_data
128	/var/lib/docker/volumes/docmost_docmost_storage/_data
49419992	/var/lib/docker/volumes/docmost_docmost_redis_data/_data
wiped docmost_docmost_postgres_data -> entries remaining: 0
wiped docmost_docmost_redis_data -> entries remaining: 0
wiped docmost_docmost_storage -> entries remaining: 0
--- sizes AFTER the wipe
0	/var/lib/docker/volumes/docmost_docmost_postgres_data/_data
0	/var/lib/docker/volumes/docmost_docmost_storage/_data
0	/var/lib/docker/volumes/docmost_docmost_redis_data/_data

--- PROOF OF LOSS through the OBSERVABLE, not the filesystem
1) the accented file:
    (empty listing above = the file is gone)
2) the app's own database — start the DB container and ask it for the rows:
    ERROR:  relation "felhom_r102_discriminator" does not exist
    LINE 1: SELECT count(*) FROM felhom_r102_discriminator;
                                 ^
    ^ an error or an empty database IS the proof: the rows cannot be read any more.

--- the PRIMARY unit is still aside:
ls: cannot access '/mnt/sys_drive/felhom-data/backups/primary/docmost': No such file or directory