From 809516b87e112259617b90675369cdb1f08bde27 Mon Sep 17 00:00:00 2001 From: clover caruso Date: Tue, 20 Oct 2026 13:02:31 -0700 Subject: [PATCH] Record SSD cache production verification Assisted-by: gpt-6-astra --- tools/zfs-read-cache.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/tools/zfs-read-cache.md b/tools/zfs-read-cache.md index 2d0466ad2bbd267cd3c77a94ea21ded5783165c8..b206f5f456271103df3f5a6382c124a19a95f79a 100644 --- a/tools/zfs-read-cache.md +++ b/tools/zfs-read-cache.md @@ -65,3 +65,18 @@ benefit requires cache hits beyond those already served by RAM; a virtualized correctness test is not a physical SSD/HDD performance benchmark. See [OpenZFS caching documentation](https://openzfs.github.io/openzfs-docs/Basic%20Concepts/Pool%20Structure/Caching.html). + +## Production rollout + +Release `40a5a3b0e724162a` activated the cache on 2026-10-20 from commit +`d7a27fd3`, after backup `20261020T195536Z-88c9a1`. The cache was online at its +configured capacity, and restarting its setup service preserved its device +GUID and contents. The pool stayed healthy with no cache I/O or checksum errors. +Approximately 50 GiB remained free on the OS SSD. + +All six previously running guests retained their VM IDs. A new disposable +guest placed its disk under `/srv/vm`, displayed its firmware shell through +the production browser console, accepted a keyboard command, and shut down +normally. Its definition and disk were removed afterward. The release's +service health checks passed. Cache warming was observed; these checks do not +establish a Windows startup speedup. -- 2.54.1