From 7b3b072295967e3c25cb7c0b939a46f34c30f935 Mon Sep 17 00:00:00 2001 From: Amos Blanton Date: Sat, 25 Sep 2021 17:27:01 +0200 Subject: [PATCH] Indicate that user may need to add vm.swapiness value if not present. My sysctl (rpi 4, latest) does not have the value vm.swapiness in it to be changed. So clarify that the value should be changed if present, otherwise add the line. --- .../04.avoid_hardware_failure/avoid_hardware_failure.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pages/01.administrate/07.specific_use_cases/05.backups/04.avoid_hardware_failure/avoid_hardware_failure.md b/pages/01.administrate/07.specific_use_cases/05.backups/04.avoid_hardware_failure/avoid_hardware_failure.md index c1a3319d..1d8e8865 100644 --- a/pages/01.administrate/07.specific_use_cases/05.backups/04.avoid_hardware_failure/avoid_hardware_failure.md +++ b/pages/01.administrate/07.specific_use_cases/05.backups/04.avoid_hardware_failure/avoid_hardware_failure.md @@ -29,7 +29,10 @@ If it is above 10: sysctl vm.swappiness=10 nano /etc/sysctl.conf ``` -And edit the value `vm.swapiness`. +If present, change the vm.swappiness value to 10. Otherwise add the line: +``` +vm.swappiness = 10 +``` ## Storage redundancy In order to limit hardware failures of storage media, it can be relevant to set up a cluster of mirrored disks (RAID, ZFS). The idea here is that everything that is written to one disk will be written to the other. This way, if one fails, the other continues to work and the server is still fully functional.