mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-11 13:17:07 +00:00
kevinveenbirkenbachandClaude Fable 5
14b41c8025
Docker mounts a volume that declares its own backing store (Options set: nfs, cifs, bind) only while a container holds it. recover.py resolved the volume's Mountpoint and rsynced into it regardless, so with the consuming stack stopped - the state its own docstring demands - the payload landed on the node's disk under the bare mountpoint directory, and the next stack start mounted the real backing store over it: a restore that reports success, delivers nothing, and leaves an invisible, unreclaimable orphan behind. That orphan had weight. In run 30859490335 the swarm drill's [9/9] volume leg restored ~1 GiB of nextcloud_data onto the manager's 30 GiB loop device in exactly the minute the device crossed SeaweedFS's 2 GiB minFreeSpace floor - the last straw on a device already >=93% consumed (the sizing is ea14535f4) - after which every authenticated Nextcloud request died on an unwritable object store. recover.py now probes the mountpoint with `mountpoint -q` (over ssh for --docker-host) whenever the volume declares Options, and dies naming the mechanism and the way out instead of writing a single byte. Plain local volumes without Options keep the old path untouched - their _data directory on the node disk is the legitimate target. The drill skips its [9/9] volume leg for such volumes with the reason in the log: its data restore already happens in [8/9] straight into the NFS export, which is the restore path the role's README prescribes for NFS-backed volumes on swarm. The leg never proved anything for them - it only filled the disk. Three new unit tests pin the contract: unmounted refused, mounted accepted, remote probed via ssh with the exact command line. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Test Utilities 🧪
This directory holds the operational side of testing in Infinito.Nexus.
These assets are meant to support confidence, not ceremony. They help the project validate real-world behavior across local development, CI environments, and deployment-oriented smoke tests. The emphasis is on practical feedback: when something breaks, the surrounding test tooling should make the failure easier to understand, easier to reproduce, and easier to clean up. 🚀
Good changes in this area usually make the test experience more:
- repeatable
- diagnosable
- environment-aware
- safe to rerun
The ideal outcome is boring reliability: contributors should be able to trust that a test run says something meaningful about the system, not just about the machine that happened to execute it. ✅