diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2017-03-25 17:37:11 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2017-03-25 17:37:11 +0200 |
| commit | 9a734661e3829fdcd89fa3cef32419d5e56b5393 (patch) | |
| tree | 4d80bc71405b08da8743cb9df21561584c0d32d5 | |
| parent | 6aead8d49c6aa020ef6630d25f30df9df1ace5d2 (diff) | |
Mention alternative SSD over-provisioning approach
| -rw-r--r-- | doc/manual.cli | 6 |
1 files changed, 5 insertions, 1 deletions
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}: |