In ESX 2.x I would have used the command, vmkpcidivy -q vmhba_devs, to get a list of DEVice names as understood by the Service Console, and also as understood by the vmkernel. The command would have given an output like so:
Why would you want this information? Well, if you have storage with some linux partitions and some blank disks, you may want to format them as VMFS-3. But you cannot ID through the VI Client which ones are blank and which ones are with Linux partitions. You might have been able to work out from the COS that /dev/sd? is a blank disk. But you might be struggling to find a way of linking this to the output in the VI client. A worry would be that you might pick the wrong disk and lose data. With the end of vmkpcidivy, you will have to find another solution. Fortunately, this is easy via the Service Console.
You can use the command esxcfg-vmhbadevs -m to see the relationship between vmhba and devnames. This produces an output like so:
vmhba0:0:0:8 /dev/sda8 443e567e-7c606397-0977-00065b0f7e2d
The command ls /vmfs/devices/disks/ will list all your disks/luns like so:vmhba0:0:0:0
You can then use fdisk to work out if the disks are blank or partitioned with:
Note: Many thanks to Satyam Vaghani of VMware, Palo Alto who helped me greatly on this.