authoravatarclover caruso<git@paperclover.net>2026-10-20 13:02:31-07:00
committeravatarclover caruso<git@paperclover.net>2026-10-21 02:52:29-07:00
log809516b87e112259617b90675369cdb1f08bde27
treedbdbf188e04d1b8e462291106ec1ce8fe49d95b8
parentaf4fd9c75c708dc3aa91fef61c46acaa82980606
signature Signed by SSH key SHA256:52mNGHRsVFBDED9IAX5pe+LRWUefqTbxEReunq21QvU

Record SSD cache production verification

Assisted-by: gpt-6-astra

1 files changed, 15 insertions(+), 0 deletions(-)

tools/zfs-read-cache.md+15
...@@ -65,3 +65,18 @@ benefit requires cache hits beyond those already served by RAM; a virtualized...@@ -65,3 +65,18 @@ benefit requires cache hits beyond those already served by RAM; a virtualized
65correctness test is not a physical SSD/HDD performance benchmark.65correctness test is not a physical SSD/HDD performance benchmark.
6666
67See [OpenZFS caching documentation](https://openzfs.github.io/openzfs-docs/Basic%20Concepts/Pool%20Structure/Caching.html).67See [OpenZFS caching documentation](https://openzfs.github.io/openzfs-docs/Basic%20Concepts/Pool%20Structure/Caching.html).
68
69## Production rollout
70
71Release `40a5a3b0e724162a` activated the cache on 2026-10-20 from commit
72`d7a27fd3`, after backup `20261020T195536Z-88c9a1`. The cache was online at its
73configured capacity, and restarting its setup service preserved its device
74GUID and contents. The pool stayed healthy with no cache I/O or checksum errors.
75Approximately 50 GiB remained free on the OS SSD.
76
77All six previously running guests retained their VM IDs. A new disposable
78guest placed its disk under `/srv/vm`, displayed its firmware shell through
79the production browser console, accepted a keyboard command, and shut down
80normally. Its definition and disk were removed afterward. The release's
81service health checks passed. Cache warming was observed; these checks do not
82establish a Windows startup speedup.