doc(volume): max volume size for the file system

Descriptions of the maximum volume size for file systems.

Ref: 7423

Signed-off-by: James Lu <james.lu@suse.com>

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

@@ -77,6 +77,7 @@ Longhorn will try to expand the file system only if:
 - The filesystem used in the Longhorn volume is one of the following:
     - ext4
     - xfs
+- The expanded size must be less than the maximum file size allowed by the file system (for example, 16TiB for `ext4`).
 - The Longhorn volume is using the block device frontend.
 
 ## Corner cases

content/docs/1.4.5/volumes-and-nodes/volume-size.md

@@ -12,6 +12,7 @@ In this section, you'll have a better understanding of concepts related to volum
 - The reason we call this field as "nominal size" is that Longhorn replicas are using [sparse files](https://wiki.archlinux.org/index.php/Sparse_file) to store data and this value is the apparent size of the sparse files (the maximum size to which they may expand). The actual size used by each replica is not equal to this nominal size.
 - Based on this nominal size, the replicas will be scheduled to those nodes that have enough allocatable space during the volume creation. (See [this doc](../node-space-usage) for more info about node allocation size.)
 - The value of nominal size determines the max available space when the volume is in use. In other words, the current active data size hold by a volume cannot be greater than its nominal size.
+- The maximum volume size is based on the disk's file system (for example, 16383 GiB for `ext4`).
 
 ## Volume `Actual Size`
 {{< figure src="/img/screenshots/volumes-and-nodes/volume-size-actual-size.png" >}}

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

@@ -77,6 +77,7 @@ Longhorn will try to expand the file system only if:
 - The filesystem used in the Longhorn volume is one of the following:
     - ext4
     - xfs
+- The expanded size must be less than the maximum file size allowed by the file system (for example, 16TiB for `ext4`).
 - The Longhorn volume is using the block device frontend.
 
 ## Corner cases

content/docs/1.5.4/volumes-and-nodes/volume-size.md

@@ -12,6 +12,7 @@ In this section, you'll have a better understanding of concepts related to volum
 - The reason we call this field as "nominal size" is that Longhorn replicas are using [sparse files](https://wiki.archlinux.org/index.php/Sparse_file) to store data and this value is the apparent size of the sparse files (the maximum size to which they may expand). The actual size used by each replica is not equal to this nominal size.
 - Based on this nominal size, the replicas will be scheduled to those nodes that have enough allocatable space during the volume creation. (See [this doc](../node-space-usage) for more info about node allocation size.)
 - The value of nominal size determines the max available space when the volume is in use. In other words, the current active data size hold by a volume cannot be greater than its nominal size.
+- The maximum volume size is based on the disk's file system (for example, 16383 GiB for `ext4`).
 
 ## Volume `Actual Size`
 {{< figure src="/img/screenshots/volumes-and-nodes/volume-size-actual-size.png" >}}

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

@@ -77,6 +77,7 @@ Longhorn will try to expand the file system only if:
 - The filesystem used in the Longhorn volume is one of the following:
     - ext4
     - xfs
+- The expanded size must be less than the maximum file size allowed by the file system (for example, 16TiB for `ext4`).
 - The Longhorn volume is using the block device frontend.
 
 ## Corner cases

content/docs/1.6.0/volumes-and-nodes/volume-size.md

@@ -12,6 +12,7 @@ In this section, you'll have a better understanding of concepts related to volum
 - The reason we call this field as "nominal size" is that Longhorn replicas are using [sparse files](https://wiki.archlinux.org/index.php/Sparse_file) to store data and this value is the apparent size of the sparse files (the maximum size to which they may expand). The actual size used by each replica is not equal to this nominal size.
 - Based on this nominal size, the replicas will be scheduled to those nodes that have enough allocatable space during the volume creation. (See [this doc](../node-space-usage) for more info about node allocation size.)
 - The value of nominal size determines the max available space when the volume is in use. In other words, the current active data size hold by a volume cannot be greater than its nominal size.
+- The maximum volume size is based on the disk's file system (for example, 16383 GiB for `ext4`).
 
 ## Volume `Actual Size`
 {{< figure src="/img/screenshots/volumes-and-nodes/volume-size-actual-size.png" >}}