aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2020-02-23 11:47:56 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2020-02-23 11:47:56 +0200
commit44690db1732b3bf864ba12afbb3e7d46225fd7e5 (patch)
tree5507b341392bb1b130e6bc7b8e981c0b3f6fa27b
parent45374ca27acd9af3d81b794ae150b6eaa6506da2 (diff)
Add note on backing up build state
-rw-r--r--doc/manual.cli7
1 files changed, 6 insertions, 1 deletions
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