Summary
When VMWare initializes a datastore, it assigns a signature/UUID to it. If a clone is made of the underlying Zadara Volume, the customer will see this new Volume in the ESXi list of devices but not on the the list of datastores as it shares a signature with an existing datastore. To solve this, they must re-signature the cloned datastore with esxcli.
Re-signaturing
To re-signature the datastore clone, you’ll need to run two commands. First, run the list command:
esxcli storage vmfs snapshot list
This should show the newly cloned datastore and provide you with a
uuid. Use that uuid to run the next command:esxcli storage vmfs snapshot resignature -u <uuid>
Shortly after this has been completed, you should see the newly cloned datastore in the list of datastores and can begin using it as normal.