docs(storage-calss-param): added details on cloneFsIdAsVolumeId

Signed-off-by: AJ_Datacore <[email protected]>

reference/storage-class-parameters.md

@@ -49,7 +49,7 @@ The `agents.core.capacity.thin` spec present in the Mayastor helm chart consists
 {% hint style="info" %}
 Note:
 1. By default, the volumes are provisioned as `thick`. 
-2. For a pool of a particular size, say 10 Gigabytes, a volume > 10 Gigabytes cannot be created, as Mayastor 2.3.0 does not support pool expansion.
+2. For a pool of a particular size, say 10 Gigabytes, a volume > 10 Gigabytes cannot be created, as Mayastor 2.4.0 does not support pool expansion.
 3. The replicas for a given volume can be either all thick or all thin. Same volume cannot have a combination of thick and thin replicas
 {% endhint %}
 
@@ -75,3 +75,10 @@ The `stsAffinityGroup` ensures that in such cases, the targets are distributed o
 
 By default, the `stsAffinityGroup` feature is disabled. To enable it, modify the storage class YAML by setting the `parameters.stsAffinityGroup` parameter to true.
 
+## "cloneFsIdAsVolumeId"
+
+`cloneFsIdAsVolumeId` is a setting for volume clones with two options: `true` and `false`. By default, it is set to `false`.
+- When set to `true`, the created clone/restore's filesystem `uuid` will be set to the new volume `uuid`. This is important because some file systems, like XFS, don't allow duplicate filesystem `uuid` on the same machine by default.
+- When set to `false`, the created clone/restore's filesystem `uuid` will be same as the orignal volume `uuid`, but it will be mounted using the `nouuid` flag to bypass duplicate `uuid` validation.
+
+