Skip to main content

Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.5, 6.7 and 7.0

  Purpose

This article provides steps to increase the disk space of a specific VMDK for the vCenter Server Appliance 6.5, 6.7 and 7.0. With the introduction of Logical Volume Management (LVM) in vSphere 6.0 and continued support with vSphere 6.5, 6.7 and 7.0, the vCenter Server disks can be dynamically increased.

List of VMDKs for a vCenter Server Appliance 6.5 - Size Mount point and Purpose

Note: Resizing the root partition (VMDK1 listed in the KB above) is not supported on 6.5. Please see the vSphere 6.5 Release Notes for more information. Resizing root partition has been added to 6.7 and 7.0.

List of VMDKs/Partitions for a vCenter Server Appliance 6.7 - Size Mount point and Purpose  

List of VMDKs/Partitions for a vCenter Server 7.0 - Size Mount point and Purpose

Note: This KB can be used for the situation like SEAT partition full or any other vCenter appliance partition full.
Resolution 
 


 

To increase the disk space:

  • Increase the virtual disk for the vCenter Server or Platform Services Controller virtual machine that is presented either via the vCenter Server or specific ESXi hypservisor managing the Virtual machines.
  • Use the Appliance Management CLI or a BASH CLI to expand the partition(s).

Using Appliance Shell

To increase the disk capacity for a specific VMDK on the vCenter Server Appliance 6.5, 6.7 and 7.0 Platform Services Controller 6.5, 6.7 and 7.0 using the Appliance Shell :
  1. Log in to the vCenter Server Appliance using SSH and root credentials.
  2. Run this command to verify which disk is experiencing disk capacity issues:
For vCenter Server Appliance 6.5:
com.vmware.appliance.version1.resources.storage.stats.list
 
For vCenter Server Appliance 6.7 and 7.0:
com.vmware.appliance.version1.resources.storage.stats.list

You see output similar to:
...
7:
Totalinodes: 655360
Usedinodes: 4211
Name: /storage/seat
Totalkbytes: 10181944
Usedkbytes: 9081843
...
  1. Using the vSphere Client or vSphere Web Client, locate the vCenter Server Appliance virtual machine and increase the disk space on the affected virtual disk. For more information, see Increasing the size of a virtual disk (1004047).

    Note: If extending VMDK size option is grayed out, the disk may be running on snapshots or the disk may be at the maximum allowed size depending on the block size of the datastore.
     
  2. After the virtual disk is increased, return to the SSH session and run this command to automatically expand any logical volumes for which the physical volumes are increased:
For vCenter Server Appliance 6.5:
com.vmware.appliance.version1.system.storage.resize

For vCenter Server Appliance 6.7 and 7.0:
com.vmware.appliance.system.storage.resize
  1. Run the command again to confirm that the virtual disk has been successfully grown:
For vCenter Server Appliance 6.5:
com.vmware.appliance.version1.resources.storage.stats.list

For vCenter Server Appliance 6.7 and 7.0:
com.vmware.appliance.version1.resources.storage.stats.list
 
You see an output similar to:
...
7:
Totalinodes: 786432
Usedinodes: 4211
Name: /storage/seat
Totalkbytes: 12246192
Usedkbytes: 9081843
...

Using BASH Shell

To increase the disk capacity for a specific VMDK on the vCenter Server Appliance 6.5, 6.7 and 7.0 using the BASH Shell:
  1. Log in to the vCenter Server Appliance using SSH and root credentials.
  2. Run this command to enable the Bash shell:

    shell.set --enabled true
     
  3. Type shell and press Enter.
  4. Use these commands to verify which disk is experiencing disk capacity issues, then trace which SCSI ID will show in the VM edit settings:

    df -h; lsblk; lsscsi
     
  5. Using the vSphere Client or vSphere Web Client, locate the vCenter Server Appliance virtual machine and increase the disk space on the affected virtual disk. For more information, see Increasing the size of a virtual disk (1004047).
     
  6. After the virtual disk is increased, return to the SSH session and run this command to automatically expand any logical volumes for which the physical volumes are increased:

    /usr/lib/applmgmt/support/scripts/autogrow.sh
     
  7. Run this command to confirm that the virtual disk has successfully grown:

    df -h
Related Information
This article is explicitly for vSphere 6.5, 6.7 and 7.0. If you are using the vCenter Server or Platform Services Controller Appliances 6.0 or 5.x, see:

Comments

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)         at com.vmware.vise.security.spring.DefaultAuthenticationProvider.logoutInternal(DefaultAuthenticationProvider.java:548)         at c

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive the error: Error connecting to <path><virtual machin

"Performance data is currently not available for this entity" viewing the performance tab

  Symptoms While accessing the performance tab and navigating to Overview, you see: No data available   The data for Real time, but fails to retrieve it for past 1 day, week, month or year.  While selecting the advance parameter in performance tab, you see: Performance data is currently not available for this entity Cause This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected. For vCenter Servers using SQL, see  "Performance data is currently not available for this entity" error after updating rollup in vSphere Resolution Backup the vCenter database. For more info