I'm on an ESXi 6.5 host using VMFS-6.
I expanded a LUN and tried to increase space on the VMFS datastore to use the new free space. It looks like the underlying partition was re-sized but the VMFS datastore might not have been?
vmkfstools -v 10 -P /vmfs/volumes/mydatastore/
VMFS-6.81 (Raw Major Version: 24) file system spanning 1 partitions.
File system label (if any): mydatastore
Mode: public
Capacity 17592186044416 (16777216 file blocks * 1048576), 7663127625728 (7308128 blocks) avail, max supported file size 70368744177664
Volume Creation Time: Thu Feb 16 00:00:30 2017
Files (max/free): 16384/16088
Ptr Blocks (max/free): 0/0
Sub Blocks (max/free): 24576/23349
Secondary Ptr Blocks (max/free): 256/255
File Blocks (overcommit/used/overcommit %): 0/9469088/0
Ptr Blocks (overcommit/used/overcommit %): 0/0/0
Sub Blocks (overcommit/used/overcommit %): 0/1227/0
Large File Blocks (total/used/file block clusters): 32768/13167/10267
Volume Metadata size: 2324496384
UUID: 58a4eb9e-865cece7-7d5a-246e96397700
Logical device: 58a4eb9e-8442b1ad-1874-246e96397700
Partitions spanned (on "lvm"):
naa.61866da0893cb3002014ac3163f4852b:1
Is Native Snapshot Capable: NO
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
This translated to a size of exactly 16TB. Now using partedUtil to see the underlying partition
partedUtil getptbl /dev/disks/naa.61866da0893cb3002014ac3163f4852b
gpt
2528380 255 63 40618426368
1 128 40618424320 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
partedUtil reports that the partition it's occupying is a full 18.9TB by calculating (last sector - first sector) * 512bytes per sector
I'm not sure what happened during the attempt to increase the datastore size but now the vsphere-client reports that there's no additional empty space to grow the datastore.
Do I need to manually grow the datastore using vmkfstools?