VMware Cloud Community
ashwinsancheti
Contributor
Contributor

LVID:579b9dec-5c208fd2-2ccd-00219b8c1fa3/579b9dec-400ad77a-8b86-00219b8c1fa3/1

what does the two GUID indicate in following information

LVID:579b9dec-5c208fd2-2ccd-00219b8c1fa3/579b9dec-400ad77a-8b86-00219b8c1fa3/1

2nd part of the GUID (579b9dec-400ad77a-8b86-00219b8c1fa3) indicates the logical device ID for given datastore.

what does the first part indicate? this is not datastore GUID.

Reply
0 Kudos
9 Replies
Finikiez
Champion
Champion

Hi!

The first one should be Device UUID, the second is VMFS UUID.

Reply
0 Kudos
ashwinsancheti
Contributor
Contributor

2nd GUID is logical device ID.

if the first GUID is device GUID then how we can get this information from vsphere api or MOB.

for each device we get LUN canonical name but not the device GUID

Reply
0 Kudos
Finikiez
Champion
Champion

To be honest I'm not sure that it's possible to get it. You can read about this numbers here

Some useful vmkfstools 'hidden' options - VMware vSphere Blog

What is the use case? Why do you need to get this UUID?

Reply
0 Kudos
ashwinsancheti
Contributor
Contributor

I am trying to use vmkfstools to get the disk block mapping.

vmkfstools -t0 /vmfs/volumes/hFiler5-AshHyperV1-FC/FC-W2K8-2/FC-W2K8-2.vmdk

Mapping for file /vmfs/volumes/hFiler5-AshHyperV1-FC/FC-W2K8-2/FC-W2K8-2.vmdk (32212254720 bytes in size):

[ 0:   188743680] --> [VMFS -- LVID:55ce07be-3055dfa2-304e-00219b8c1fa3/55ce07be-1bf25cac-5189-00219b8c1fa3/1:( 40305164288 -->  40493907968)]

according to above output

Device GUID: 55ce07be-3055dfa2-304e-00219b8c1fa3

vmfs GUID : 55ce07be-1bf25cac-5189-00219b8c1fa3

when i run following command i dont see any VMFS GUID matching with above VMFS GUID.

[root@light:~] esxcli storage vmfs extent list

Volume Name                                 VMFS UUID                            Extent Number  Device Name                           Partition

------------------------------------------  -----------------------------------  -------------  ------------------------------------  ---------

hFiler5-AshHyperv1-FC_2                55cce2da-1b97eb40-2248-00219b8c1fa3              0  naa.60a98000316b2f59635d4664664d7546          1

Douglas_Datastore                           5775684c-055fa02e-1284-00219b8c1fa3              0  naa.60a98000316b2f59635d466466536b4e          1

Storage_1                                        4a395ca6-e558e624-43ea-00219b8c1fa1              0  naa.5000cca21ed1ae48                          3

STORAGE01                                   49a44553-fdafdd40-403e-00219b8c1fa3              0  naa.5000cca21ed16338                          1

PureStorage-Rahil-Vol2                    545798b0-5853c62a-478f-00219b8c1fa3              0  naa.624a9370c9cfbacd653c81f200011125          1

hFiler5-AshHyperV1-FC                    55ce07be-3423888e-577c-00219b8c1fa3              0  naa.60a98000316b2f59635d4664664d7575          1

hFiler5-AshHyperV1-FC                    55ce07be-3423888e-577c-00219b8c1fa3              1  naa.60a98000316b2f59635d4664664f5933          1

OracleZFS_ds                                   538655d4-2bffb240-432c-00219b8c1fa3              0  naa.600144f0b1a25c7f0000538659d02de8          1

SarathNimbleDS                                59a5afa2-7779b274-9805-00219b8c1fa3              0  eui.c6f3affc2eb60c496c9ce900e2faddce          1

Actual VMFS GUID for datastore hFiler5-AshHyperV1-FC is 55ce07be-3423888e-577c-00219b8c1fa3

first part and last of the GUID is matching with 55ce07be-1bf25cac-5189-00219b8c1fa3 but middle portion is not matching.

Am i missing anything here?

also not able to find any command to get device GUID.

any help will be really appreciated.

-Ashwin

Reply
0 Kudos
Finikiez
Champion
Champion

I presume that Disk UUID is only possible to get through disklib as all common utilities don't use it.

Also I don't think that it's a proper way to understand on which extent resides a vmdk file if it's that you want to get.

Do you get proper VMFS UUID if you check block mapping for a vmdk which is on a single extent vmfs datastore?

Reply
0 Kudos
ashwinsancheti
Contributor
Contributor

No.

I don’t get proper VMFS UUID even for single extent datastor.

Reply
0 Kudos
Finikiez
Champion
Champion

Intresting thing. I have the same behaviour in my lab

For example

# vmkfstools -t10 /vmfs/volumes/HDS_AMS2500_SAS_LUN0/psc01/psc01.vmdk

Mapping for file /vmfs/volumes/HDS_AMS2500_SAS_LUN0/psc01/psc01.vmdk (42949672960 bytes in size):

[           0:     1048576] --> [VMFS -- LVID:56d0625d-af181abf-ca51-002128a2b0dc/56d0625d-995ecc5c-4c04-002128a2b0dc/1:( 2114596110336 -->  2114597158912)]

[     1048576:    97517568] --> [VMFS -- LVID:56d0625d-af181abf-ca51-002128a2b0dc/56d0625d-995ecc5c-4c04-002128a2b0dc/1:( 2119026343936 -->  2119123861504)]

[    98566144:     8388608] --> [NOMP -- Smiley Sad           0 -->      8388608)]

[   106954752:     5242880] --> [VMFS -- LVID:56d0625d-af181abf-ca51-002128a2b0dc/56d0625d-995ecc5c-4c04-002128a2b0dc/1:( 2119123861504 -->  2119129104384)]

and etc..

however there is no similar UUID in output esxcli storage vmfs extent list

/vmfs/volumes/56d0625e-a30d852c-af48-002128a2b0dc/psc01 # esxcli storage vmfs extent list

Volume Name                VMFS UUID                            Extent Number  Device Name                           Partition

-------------------------  -----------------------------------  -------------  ------------------------------------  ---------

....

HDS_AMS2500_SAS_LUN0       56d0625e-a30d852c-af48-002128a2b0dc              0  naa.60060e80100cfdf0053047e700000000          1

But I looked into output  of another command and see both UUIDs

# vmkfstools -P -v10 /vmfs/volumes/HDS_AMS2500_SAS_LUN0

VMFS-5.60 file system spanning 1 partitions.

File system label (if any): HDS_AMS2500_SAS_LUN0

Mode: public ATS-only

Capacity 2198754820096 (2096896 file blocks * 1048576), 195887628288 (186813 blocks) avail, max file size 69201586814976

Volume Creation Time: Fri Feb 26 14:34:06 2016

Files (max/free): 130000/128817

Ptr Blocks (max/free): 64512/59694

Sub Blocks (max/free): 32000/31801

Secondary Ptr Blocks (max/free): 256/256

File Blocks (overcommit/used/overcommit %): 0/1910083/0

Ptr Blocks  (overcommit/used/overcommit %): 0/4818/0

Sub Blocks  (overcommit/used/overcommit %): 0/199/0

Volume Metadata size: 814383104

UUID: 56d0625e-a30d852c-af48-002128a2b0dc

Logical device: 56d0625d-995ecc5c-4c04-002128a2b0dc

Partitions spanned (on "lvm"):

        naa.60060e80100cfdf0053047e700000000:1

Is Native Snapshot Capable: YES

OBJLIB-LIB: ObjLib cleanup done.

So it might be that blog post from 2012 year is not 100% accurate. But this won't help you get Device UUID, sorry Smiley Happy

Reply
0 Kudos
ashwinsancheti
Contributor
Contributor

Thanks for your help.

Hoping to get clear answer from someone.

Reply
0 Kudos
ashwinsancheti
Contributor
Contributor

does anyone have answer for this?

Reply
0 Kudos