To list the volumes detected as snapshots, run this command:

# esxcli storage vmfs snapshot list

OR
# esxcfg-volume -l
To check whats mounted
#esxcli storage filesystem list
To mount a snapshot/replica LUN that is persistent across reboots, run this comm
and:
# esxcli storage vmfs snapshot mount -l label
# esxcli storage vmfs snapshot mount -l "VMFS_1"
# esxcli storage vmfs snapshot mount -u "49d22e2e-996a0dea-b555-001f2960aed8"
OR
#esxcfg-volume -m 4fbfff40-d0358207-e61a-d067e5face92.
To mount a snapshot/replica LUN that is not persistent across reboots, run this
command
# esxcli storage vmfs snapshot mount -n -l "VMFS_1"
# esxcli storage vmfs snapshot mount -n -u "49d22e2e-996a0dea-b555-001f2960aed8"
To resignature a snapshot/replica LUN (the volume is mounted immediately after t
he resignature), run this command:
Further Troubleshooting
# esxcli storage vmfs snapshot extent list
# esxcli system settings advanced list option /LVM/EnableResignature
# esxcli system settings advanced list option /LVM/DisallowSnapshotLUN
echo 0 > /proc/vmware/config/LVM/DisallowSnapshotLUN
echo 1 > /proc/vmware/config/LVM/EnableResignature
Brief Note
1. EnableResignature=0, DisallowSnapshotLUN=1 (default)
In this state, you cannot bring snapshots or replicas of VMFS volumes by the arr
ay into the ESX Server host regardless of whether or not the ESX Server has acce
ss to the original LUN. LUNs formatted with VMFS must have the same ID for each
ESX Server host.
2. EnableResignature=1, (DisallowSnapshotLUN is not relevant)
In this state, you can safely bring snapshots or replicas of VMFS volumes into t
he same servers as the original and they are automatically resignatured.
3. EnableResignature=0, DisallowSnapshotLUN=0 (This is similar to ESX Server 2.x
behavior.)
In this state, the ESX Server assumes that it sees only one replica or snapshot
of a given LUN and never tries to resignature. This is ideal in a DR scenario wh
ere you are bringing a replica of a LUN to a new cluster of ESX Servers, possibl
y on another site that does not have access to the source LUN. In such a case, t
he ESX Server uses the replica as if it is the original.
# esxcli storage vmfs snapshot resignature -l "VMFS_1"
# esxcli storage vmfs snapshot resignature -u "49d22e2e-996a0dea-b555-001f2960ae
d8"