Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

The storage/core filesystem is out of disk space or inodes alert in vCenter Server Appliance Health Status (50465)

Last Updated: 4/12/2024Categories: TroubleshootingTotal Views: 1632Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The storage/core filesystem is out of disk space or inodes

Logging into the VCSA via SSH and running ‘df –h’ shows that  /storage/core is 100% utilized

Performing the command "ls -lah" on the /storage/core directory shows log bundles (filenames and timestamps may vary and are included for example purposes only):

vcsa01:/storage/core # df -h
Filesystem                            Size  Used Avail Use% Mounted on
/dev/sda3                              11G  3.9G  6.3G  39% /
udev                                  4.0G  168K  4.0G   1% /dev
tmpfs                                 4.0G   40K  4.0G   1% /dev/shm
/dev/sda1                             128M   38M   84M  31% /boot
/dev/mapper/core_vg-core               25G   25G    0M 100% /storage/core
/dev/mapper/log_vg-log                9.9G  209M  9.2G   3% /storage/log
/dev/mapper/db_vg-db                  9.9G  192M  9.2G   3% /storage/db
/dev/mapper/dblog_vg-dblog            5.0G  171M  4.5G   4% /storage/dblog
/dev/mapper/seat_vg-seat              9.9G  165M  9.2G   2% /storage/seat
/dev/mapper/netdump_vg-netdump       1001M   18M  932M   2% /storage/netdump
/dev/mapper/autodeploy_vg-autodeploy  9.9G  151M  9.2G   2% /storage/autodeploy
/dev/mapper/invsvc_vg-invsvc          5.0G  146M  4.6G   4% /storage/invsvc

Cause

Log bundles created by vm-support command and/or by "export system logs" in the vSphere Client are not removed when completed.

Impact / Risks

This process can cause irreversible damage to files if done incorrectly.If in doubt, open a Support Request with VMware Technical Support!

Can fill up the available space on the vCSA causing the web client to become unresponsive and/or not display the inventory.

Resolution

Take a snapshot of the vCenter Server Appliance

Stop the vpxd service by running the command service vmware-vpxd stop

Verify the service has stopped by running the command service vmware-vpxd status; you should see "vmware-vpxd is stopped"

Remove the .tgz files by using the ‘rm’ command. For example: rm vc-vcsa10-216-08-28-14.17.tgz

Repeat as needed.

Once this is done, confirm that there is now free space in the /storage/core area by running the "df -h" command:

Filesystem                            Size  Used Avail Use% Mounted on /dev/sda3
/udev                                  4.0G  168K  4.0G   1% /dev
/tmpfs                                 4.0G   40K  4.0G   1% /dev/shm
/dev/sda1                             128M   38M   84M  31% /boot
/dev/mapper/core_vg-core               25G  173M   24G   1% /storage/core
/dev/mapper/log_vg-log                9.9G  209M  9.2G   3% /storage/log/dev/mapper/db_vg-db                  9.9G  192M  9.2G   3% /storage/db
/dev/mapper/dblog_vg-dblog            5.0G  171M  4.5G   4% /storage/dblog
/dev/mapper/seat_vg-seat              9.9G  165M  9.2G   2% /storage/seat
/dev/mapper/netdump_vg-netdump       1001M   18M  932M   2% /storage/netdump
/dev/mapper/autodeploy_vg-autodeploy  9.9G  151M  9.2G   2% /storage/autodeploy
/dev/mapper/invsvc_vg-invsvc          5.0G  146M  4.6G   4% /storage/invsvc

Start the vpxd service by running the command “service vmware-vpxd start.”  The error alarm should now clear in vCenter.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
ESXi의 "확실하지 않은 상태; 빠른 경로 상태 업데이트를 요청함(state in doubt; requested fast path state update)" 오류 (1022026)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESXi 6.0、6.5 で競合状態が発生し、仮想マシンまたは hostd 管理サービスが中断される (50372)

KB
•
Servicio de rendimiento: modo detallado en el servicio de estado de vSAN (51527)

KB
•
同一 vCenter 的不同 vmkernel 中可能会显示重复的 MAC 地址 (52035)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.0.x

Take Our Survey

Support Assistant