1 Reply Latest reply on Jun 9, 2020 7:05 AM by lucasbernadsky

    [ESXi 6.7 vmfs-6] How does "esxcli storage vmfs snapshot list" find the datastores?

    ziffusion Lurker

      On ESXi 6.7 vmfs-6.


      The command "esxcli storage vmfs snapshot list" is showing me a datastore that I cannot find in any vmfs partition. Where would it be finding this datastore?


      My understanding is that vmfs finds datastores by scanning all the disks - by looking in the partition table for partitions of type vmfs, and then looking for metadata in these partitions. The first extent is supposed to contain the name of the datastore and the list of disk:partitions on which the extents exist.


      My problem is that the command show me a datastore that is not present in the meta-data of any of the vmfs partitions. I'd like to find out where it is finding this datastore.


      Any help will be highly appreciated.

        • 1. Re: [ESXi 6.7 vmfs-6] How does "esxcli storage vmfs snapshot list" find the datastores?
          lucasbernadsky Enthusiast

          Hi zifussion.

          It has never happend to me before. Have you tried rescanning all storage devices?


          I found this VMware KB that maybe explains your problem: VMware Knowledge Base


          "The snapshot LUNs issue occurs when the ESXi/ESX host does not confirm the identity of the LUN with what it expects to see in the VMFS metadata. This issue occurs after replacing SAN hardware, firmware upgrades, SAN replication, DR tests, and some HBA firmware upgrades. This issue also occurs in some ESXi/ESX host upgrades from 3.5 to 4.x (due to the change in naming convention from mpx to naa). However, this is a rare occurrence. For more/related information, see the Managing Duplicate VMFS Datastores in the ESX Configuration Guide for ESXi/ESX 4.x and vSphere Storage Guide for ESXi 5.x and 6.x."


          When one ESXi/ESX host force mounts a VMFS datastore residing on a LUN is detected as a snapshot, an object is added to the datacenter grouping in the vCenter Server database to represent that datastore.


          When a second ESXi/ESX host attempts to do the same operation on the same VMFS datastore, the operation fails because an object already exists within the same datacenter grouping in the vCenter Server database.


          Because an object already exists, vCenter Server does not allow mounting the datastore on any other ESXi/ESX host residing in that same datacenter.



          Hope this fit your issue