more docs
This commit is contained in:
1 parent
30427e3975
commit
053b9c4c95
2 files changed
+176
-45
No files matched your search
@@ -12,6 +12,21 @@ Shared model for everything else in these docs. Read once; other pages assume it
|
||||
System is large, churny, rebuildable from this flake. State holds what cannot
|
||||
be reproduced — snapshots stay cheap.
|
||||
|
||||
Snapshots run **hourly by default** (systemd timer with `OnCalendar = "hourly"`)
|
||||
and keep the last 48. They only cover the state disk. See [RECOVERY.md](RECOVERY.md#snapshots)
|
||||
for details and how to adjust `services.hermenix.snapshots.interval` / `keep`.
|
||||
|
||||
**Btrfs + nodatacow design note.** The state disk image is stored on a btrfs
|
||||
subvolume with `chattr +C` (nodatacow). This is intentional: CoW under a VM
|
||||
disk image causes terrible fragmentation. However, a btrfs snapshot of a
|
||||
nodatacow subvolume re-enables CoW for any blocks the snapshot still
|
||||
references. Live snapshots therefore increase fragmentation and the amount of
|
||||
data that later changes (affecting both guest performance and backup size).
|
||||
Snapshots and backups are independent; pruning snapshots improves both.
|
||||
See [RECOVERY.md](RECOVERY.md#snapshots) and [RECOVERY.md](RECOVERY.md#backups)
|
||||
for retention advice and why backups are file-level tars over vsock rather
|
||||
than disk images.
|
||||
|
||||
Host images under `services.hermenix.disk.baseDir` (default `/var/lib/hermes-vm`):
|
||||
|
||||
```
|
||||
|
||||
Reference in new issue
Block a user