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

"VASpace (08/13) DiskDump: Partial Dump: Out of space o=0x63ff800 l=0x1000" error in ESXi host (59256)

Last Updated: 10/20/2020Categories: TroubleshootingTotal Views: 6305Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When the dump file generated by PSOD is larger than the file which previously set to the diagnostic partition or slot size, you experience these symptoms:

ESXi host generates Partial Dump.

You see the PSOD:

VASpace (08/13) DiskDump: Partial Dump: Out of space o=0x63ff800 l=0x1000

In the /var/log/vobd.log file, you see log entries similar to:

YYYY-MM-DDTHH:MM:SS.XXXZ: [GenericCorrelator] 42315340us: [vob.user.coredump.capacity.insufficient] The storage capacity of the coredump targets is insufficient to capture a complete coredump. Recommended coredump capacity is 299 MiB.

Cause

This issue occurs when the generated dump size is larger than the size which was previously set to the diagnostic partition or slot size. By default, the diagnostic partition is 2.5GB.

Note: The dump size varies depending on the environment and operation. Compared to non-vSAN environment, in vSAN environments dump files tend to larger. Therefore, in the large scale environment, highly loaded environment, and vSAN environment, you must change the slot size and the partition size.

Resolution

To resolve this issue:

In a vSAN environment, see Extending an ESXi diagnostic coredump partition on a vSAN 6.5/6.6 node (2147881).

In a non-vSAN environment, extend the diagnostic partition and/or the slot size according to the environment.

Notes:

The size should be larger than [Recommended coredump capacity] described in /var/log/vobd.log file.

When the size is not described in /var/log/vobd.log file, VMware recommends to set the slot size to more than 300MB.

Diagnostic partition is set as 2.5GB by default.

When you set the slot size to more than 2.5 GB, you must set the dump partition in advance.

To check the diagnostic partition:

Check the current diagnostic partition by running the esxcli command using ESX shell or SSH. For more information to use ESX shell or SSH, see Using ESXi Shell in ESXi 5.x and 6.x (2004746).

For example:

# esxcli system coredump partition list

Name                   Path                                       Active  Configured
---------------------  -----------------------------------------  ------  ----------
mpx.vmhba1:C0:T0:L0:7  /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:7   false       false
mpx.vmhba1:C0:T0:L0:9  /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:9    true        true

If the [Active] field is true (the ninth partition of mpx.vmhba1:C0:T0:L0:9), the partition is set as the diagnostic partition. For more information, see Configuring a diagnostic coredump partition on an ESXi 5.x/6.x host (2004299).

Check the diagnostic partition size with partedUtil command. Specify the disk that includes the diagnostic partition, and check the line where the first field is partition number of the diagnostic partition.

For example:

# partedUtil getptbl "/vmfs/devices/disks/mpx.vmhba1:C0:T0:L0"

gpt
1305 255 63 20971520
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
3 15472640 20971486 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

Check the sector number from the second (starting sector) and third (ending sector) field.

Multiply the number by 512, and convert it to a byte unit.

For example:
(7086080 - 1843200) * 512 = 2684354560 [Bytes]

For more information, see Using the partedUtil command line utility on ESXi and ESX (1036609).

To expand the diagnostic partition:

Expand or create a diagnostic partition with partedUtil command. For more information, see Configuring a diagnostic coredump partition on an ESXi 5.x/6.x host (2004299).

To check the slot size:

Using the Web Client, select the ESXi host.

Click the Configure tab.

Select the Advanced System Settings.

Enter SlotSize into the [Filter] option on the right side, and search the correct parameter.

Select the [VMkernel.Boot.diskDumpSlotSize] option (the unit is MB).

To expand the slot size:

Using the Web Client, select the ESXi host.

Click the Configure tab.

Select the Advanced System Settings.

Enter SlotSize into the Filter option on the right side, and search the correct parameter.

The VMkernel.Boot.diskDumpSlotSize option is displayed on the list.

On the right pane of the Advanced System Settings page, select the option, and click Edit.

Change the slot size to the desired value and click OK.

Related Information

ESXi hosts with larger workloads may generate partial core dumps (2012362)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

KB
•
テンプレートの VMDK ファイルがロックされているためにテンプレートから仮想マシンをデプロイできない (1007487)

KB
•
注册 vCenter Server 后，Usage Meter 无法发现 vRealize Operations Manager (58549)

KB
•
Intel X710/X722 ネットワーク リンクでドライバ i40en が PF リセットを発行したときにホストがネットワーク接続を失う (59568)

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 vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant