VSPHERE 4.1 VMFS resize

[OmniTech]

Hi!

Is it possible to resize a VMFS volume that was created without the "Maximize Capacity" check box?

In the GUI of virtual center, it don't seem to see that there is free space not used because the checkbox "Maximize Capacity" was not used the first time.

Thanks!

[a_p_]

Some questions:

Is the free disk space adjacent to the VMFS partition?

Is the datastore created on a local (DAS) disk or on a storage LUN?

Depending on the current partitioning http://kb.vmware.com/kb/1009125 may help.

André

[AndreTheGiant]

Are you sure that there is additional space? Check partition layout with fdisk -l command. Or on datastore properties.

Andre

[OmniTech]

Yes, I'm sure.

I created a LUN of 100gb and in VCenter I can see that only 92gb are usable.

So I guess the VMFS volume was created without the "maximize capacity" checkbox.

[AndreTheGiant]

But the GUI report 100GB as a datastore size or 92?

Some space is needed by VMFS metadata, but it not so big.

What's the output of

fdisk -l

[OmniTech]

No, the GUI reports 92gb. I can see on the SAN's GUI that the LUN is 100gb capacity.

Disk /dev/sdd: 99.6 GB, 99683221504 bytes

255 heads, 63 sectors/track, 12119 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdd1               1       12119    97345803+  fb  VMware VMFS

[AndreTheGiant]

From fdisk the disk size is correct (99.6) and the partition goes to the last cylinder (12119).

Andre

[OmniTech]

But is the VMFS volume really takes 8gig for metadata? Seems a bit too much

[a_p_ · Accepted solution]

No, the GUI reports 92gb. I can see on the SAN's GUI that the LUN is 100gb capacity

IMO everything is correct. 100GB SAN = 92 GB VMFS

It looks like your SAN is reporting the gigabytes with a factor of 1,000, whereas VMware uses 1,024 which is technically correct.

99,683,221,504 bytes / 1,024 / 1,024 / 1,024 = 92.84 GB

André