I thought I had an idea about how ESXi detects a VMFS-volume but it seems I was wrong.
Questions:
How is it possible that VOMA used with a command like
voma -m vmfs -f check -d /vmfs/devices/disks/naa.6a4badb009606100ff00003f0401e488:1
lists a different UUID as the one I see with hexdump -C
00100200 00 00 00 b0 d1 01 00 00 1c 1d 00 00 00 00 00 00 |................|
00100210 01 00 00 00 35 31 32 36 35 61 34 35 2d 32 64 37 |....51265a45-2d7|
00100220 37 32 34 34 30 2d 31 31 37 61 2d 30 30 32 34 38 |72440-117a-00248|
00100230 31 65 35 62 63 34 36 00 00 00 00 00 00 00 00 00 |1e5bc46.........|
00100240 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
How is it possible that the content of a datastore disappears and reappears by a reboot ?
How is it possible that sometimes a datastore is listed and content seems to be there even without valid partition table ?
How is it possible that the Linux vmfs-fuse driver often lists the content of a datastore when ESXi says the datastore is empty ?
How is it possible that a datastore disaapears and reappears with esxcli storage filesystem automount ?
How is this possible ?
~ # esxcli storage filesystem mount --volume-label="datastorebig"
No volume with label 'datastorebig' was found
~ # esxcli storage filesystem automount
~ # esxcli storage filesystem mount --volume-label="datastorebig"
Volume 'datastorebig' is already mounted
Where does ESXi store the VMFS-labels ?