Quantcast
Channel: VMware Communities : Discussion List - ESXi
Viewing all articles
Browse latest Browse all 8132

Issue after resizing datastore from GUI

$
0
0

Hi,

 

I'm trying to solve the same problem and running into the same issue. Unfortunately I don't find a solution here and I want to ask if there has been news about this particular problem.

 

One of my servers in my homelab was slowly running out of physical space and I have extended my virtual disk by 4TB which went fine after my H700 controller was busy the last 4 days. As the next step I've extended the Datastore via the GUI, but that did only half of the job.

 

I've ended up with my partition fully resized from 5,6TB to 9.09TB.

 

esxi1.jpg

But - same issue as the TO - the shown capacity is still the old value of 5.45 TB:

 

esxi2.jpg

 

The "vmkfstools --growfs" command is just broken, I'm getting the same stupid error as the TO. The partition 3 of naa.xxxx shows at the right size:

 

[root@VMServer2:/dev/disks] ls -l
total 19540937520
-rw-------    1 root     root     7850688512 Dec 21 17:00 mpx.vmhba32:C0:T0:L0
-rw-------    1 root     root       4161536 Dec 21 17:00 mpx.vmhba32:C0:T0:L0:1
-rw-------    1 root     root     262127616 Dec 21 17:00 mpx.vmhba32:C0:T0:L0:5
-rw-------    1 root     root     262127616 Dec 21 17:00 mpx.vmhba32:C0:T0:L0:6
-rw-------    1 root     root     115326976 Dec 21 17:00 mpx.vmhba32:C0:T0:L0:7
-rw-------    1 root     root     299876352 Dec 21 17:00 mpx.vmhba32:C0:T0:L0:8
-rw-------    1 root     root     2684354560 Dec 21 17:00 mpx.vmhba32:C0:T0:L0:9
-rw-------    1 root     root     9999220736000 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e
-rw-------    1 root     root       4161536 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e:1
-rw-------    1 root     root     4293918720 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e:2
-rw-------    1 root     root     9991298727424 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e:3
-rw-------    1 root     root     262127616 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e:5
-rw-------    1 root     root     262127616 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e:6
-rw-------    1 root     root     115326976 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e:7
-rw-------    1 root     root     299876352 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e:8
-rw-------    1 root     root     2684354560 Dec 21 17:00 naa.6782bcb0349bdb00ff00005f05e6a18e:9

 

But the "growfs" command fails:

 

[root@VMServer2:/dev/disks] vmkfstools --growfs "naa.6782bcb0349bdb00ff00005f05e6a18e:3" "naa.6782bcb0349bdb00ff00005f05e6a18e:3"
Not found
Error: No such file or directory

 

I'm pretty sure to use the right syntax for the "vmkfstools" command - what am I doing wrong? And how can I get the capacity of my datastore fixed, so that it uses the additional 3.6TB which is already in the partition?


Viewing all articles
Browse latest Browse all 8132

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>