Fix incorrect value of default setting StorageMinimalAvailablePercent…

…age.

Signed-off-by: James Munson <james.munson@suse.com>

content/docs/1.4.0/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `200` (%). That means we can schedule a total of 300 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.4.1/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `200` (%). That means we can schedule a total of 300 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.4.2/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `200` (%). That means we can schedule a total of 300 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.4.3/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `200` (%). That means we can schedule a total of 300 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.4.4/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `200` (%). That means we can schedule a total of 300 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.4.5/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `200` (%). That means we can schedule a total of 300 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.5.0/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `100` (%). That means we can schedule a total of 150 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.5.1/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `100` (%). That means we can schedule a total of 150 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.5.2/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `100` (%). That means we can schedule a total of 150 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.5.3/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `100` (%). That means we can schedule a total of 150 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.5.4/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `100` (%). That means we can schedule a total of 150 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.

content/docs/1.6.0/volumes-and-nodes/multidisk.md

@@ -44,7 +44,7 @@ Once those two conditions are met, you should be allowed to remove the disk.
 There are two global settings affect the scheduling of the volume.
 
 - `StorageOverProvisioningPercentage` defines the upper bound of `ScheduledStorage / (MaximumStorage - ReservedStorage)`. The default value is `100` (%). That means we can schedule a total of 150 GiB Longhorn volumes on a 200 GiB disk with 50G reserved for the root file system. Because normally people won't use that large amount of data in the volume, and we store the volumes as sparse files.
-- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `10` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
+- `StorageMinimalAvailablePercentage` defines when a disk cannot be scheduled with more volumes. The default value is `25` (%). The bigger value between `MaximumStorage * StorageMinimalAvailablePercentage / 100` and `MaximumStorage - ReservedStorage` will be used to determine if a disk is running low and cannot be scheduled with more volumes.
 
 Notice that currently there is no guarantee that the space volumes use won't exceed the `StorageMinimalAvailablePercentage`, because:
 1. Longhorn volumes can be bigger than the specified size, due to fact that the snapshot contains the old state of the volume.