From 44690db1732b3bf864ba12afbb3e7d46225fd7e5 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Sun, 23 Feb 2020 11:47:56 +0200 Subject: Add note on backing up build state --- doc/manual.cli | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/manual.cli b/doc/manual.cli index 1529ca8..5187e87 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -217,7 +217,7 @@ The stored state is fairly small (hundreds of megabytes) and is not performance-critical. While one can create a small state partition on the same physical disk as used for machines (see below), having it on a separate disk makes it easier to move machine disks around. Based on these requirements, a -small USB flash drive or flash card is a good option. +small, good-quality USB flash drive or flash card is a good option. While any suitable filesystem can be used, \c{ext4} is a good choice, with journaling disabled if used on a flash drive/card. For example: @@ -226,6 +226,11 @@ journaling disabled if used on a flash drive/card. For example: mkfs.ext4 -L buildos.state -O ^has_journal /dev/sdX \ +\N|Flash drives and cards tend to fail over time and while the state is not +precious, recreating it would also require updating the public key on all the +controllers that this build host serves. As a result, it may be prudent to +backup it up.| + \h2#config-storage-machines|Machines| For virtual machine and container storage we can use a single disk, in which -- cgit v1.1