From 9a734661e3829fdcd89fa3cef32419d5e56b5393 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Sat, 25 Mar 2017 17:37:11 +0200 Subject: Mention alternative SSD over-provisioning approach --- doc/manual.cli | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/manual.cli b/doc/manual.cli index 863841c..eae02d3 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -175,7 +175,7 @@ interrupted with a shell prompt where you can format and/or lable a suitable disk. You can also view the storage configuration on a booted Build OS instance by examining \c{/etc/fstab}. -As an example, let's consider the first boot of a clean machine that has a 1TB +As an example, let's consider the first boot of a clean machine that has an SSD disk as \c{/dev/sda} and which we would like to use for virtual machine storage. We would also like to over-provision this SSD by 10% to (potentially) prolong its life and increase performance (you may want to skip this step if @@ -193,6 +193,10 @@ over-provision the disk: # ^D # Exit shell and reboot. \ +Note that this may not always work, depending on the disk controller used. An +alternative approach is to use the \c{mkfs.btrfs --byte-count} option when +formatting the disk to leave some disk space untouched and unused. + After the reboot we will be presented with a shell prompt again where we confirm over-provisioning, format the disk as \c{btrfs}, and label it as \c{buildos.machines}: -- cgit v1.1