== A1 CONTROL: the old-form copy, undamaged, --appendonly yes
   state: running exit=0
   dbsize: 129  probe key 7: v7-7c5…
   log: 1:M 17 Oct 2026 07:12:20.835 * DB loaded from base file appendonly.aof.1.base.rdb: 0.000 seconds
   log: 1:M 17 Oct 2026 07:12:20.836 * DB loaded from incr file appendonly.aof.1.incr.aof: 0.001 seconds
   log: 1:M 17 Oct 2026 07:12:20.836 * DB loaded from append only file: 0.001 seconds
   log: 1:M 17 Oct 2026 07:12:20.836 * Ready to accept connections tcp
== A2 the old form, damaged the 2026-09-24 way: 64 zero bytes written INTO the AOF, 400 bytes before its end
   file 35789 bytes, zeros at 35389..35452; size after 35789
   state: exited exit=1
   dbsize: Error response from daemon: container 5abf3c47a6d2e027686392724cfe7b5fb4b76c42db45439d70ec283975512e25 is not running  probe key 7: Error …
   log: 1:C 17 Oct 2026 07:12:25.564 * Configuration loaded
   log: 1:M 17 Oct 2026 07:12:25.567 * Done loading RDB, keys loaded: 0, keys expired: 0.
   log: 1:M 17 Oct 2026 07:12:25.567 * DB loaded from base file appendonly.aof.1.base.rdb: 0.000 seconds
   log: 1:M 17 Oct 2026 07:12:25.568 # Bad file format reading the append only file appendonly.aof.1.incr.aof: make a backup of your AOF file, then use ./redis-check-aof --fix <filename.manifest>
== R1 the NEW form on a FULL disk (tmpfs 1 MiB): a save that cannot be written
OK
0b04403f53805a16d01d10b490b70bcc7045c381dedd834acf449317f5f33d74  /data/r/dump.rdb
total 4
drwxr-xr-x    2 redis    root            60 Oct 17 07:12 .
drwxr-xr-x    3 redis    redis           80 Oct 17 07:12 ..
-rw-r--r--    1 redis    redis         1126 Oct 17 07:12 dump.rdb
   now 1.2 MB of new data, which cannot fit:
Background saving started
rdb_changes_since_last_save:1
rdb_last_bgsave_status:err
MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

0b04403f53805a16d01d10b490b70bcc7045c381dedd834acf449317f5f33d74  /data/r/dump.rdb
total 4
drwxr-xr-x    2 redis    root            60 Oct 17 07:12 .
drwxr-xr-x    3 redis    redis           80 Oct 17 07:12 ..
-rw-r--r--    1 redis    redis         1126 Oct 17 07:12 dump.rdb
tmpfs                     1024         8      1016   1% /data
16:M 17 Oct 2026 07:12:31.495 * Background saving started by pid 91
91:C 17 Oct 2026 07:12:31.506 # Write error while saving DB to the disk(rdbSaveRio): No space left on device
16:M 17 Oct 2026 07:12:31.560 # Background saving error
   stop WITHOUT saving (what a kill does), start again on the same folder:
   dbsize after start: 50  probe 7: v7
109:M 17 Oct 2026 07:12:34.604 * Done loading RDB, keys loaded: 50, keys expired: 0.
== R2 what a TRUNCATED dump.rdb does (half the file) — the shape the temp-file-and-rename write never leaves behind
   dump.rdb cut from 14378 to 7189 bytes
   state: exited exit=1
   dbsize: Error response from daemon: container 5d3c6d322f4553552f6fdae5e1eea896a8fb9ab9b42a364b7fd0b03099ae9e90 is not running  probe key 7: Error …
   log: 1:M 17 Oct 2026 07:12:36.127 # Internal error in RDB reading offset 0, function at rdb.c:2818 -> Stream listpacks loading failed.
   log: --- RDB ERROR DETECTED ---
   log: [offset 6493] Internal error in RDB reading offset 0, function at rdb.c:2818 -> Stream listpacks loading failed.
   log: [info] 2 already expired
== cleanup: 0 r1096-* containers left
