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

"No space for journal on volume" errors observed on VMFS6 datastores (67896)

Last Updated: 2/23/2024Categories: Known IssueTotal Views: 15378Language:
English

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

Unable to power on newly created VMs, as there is no free space for journal on volumes.

Existing VMs continue to run.

Logs show similar to below

vmkernel logs:

YYYY-MM-DDTHH:MM:SS.617Z cpu23:67366)WARNING: HBX: 274: No space for the journal on volume UUID (Datastore name). Volume will remain in read-only metadata mode with limited write support until journal can be created.
YYYY-MM-DDTHH:MM:SS.617Z cpu9:67366)FS3J: 1513: Could not allocate a journal. Garbage collect on vol 'Datastore name'

Hostd logs:

YYYY-MM-DDTHH:MM:SS.617Z info hostd[13DC1B70] [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {
--> key = -1,
--> chainId = 778133870,
--> createdTime = "1970-01-01T00:00:00Z",
--> userName = "",
--> datacenter = (vim.event.DatacenterEventArgument) null,
--> computeResource = (vim.event.ComputeResourceEventArgument) null,
--> host = (vim.event.HostEventArgument) {
--> name = "ESX Host",
--> host = 'vim.HostSystem:ha-host'
--> },
--> vm = (vim.event.VmEventArgument) null,
--> ds = (vim.event.DatastoreEventArgument) null,
--> net = (vim.event.NetworkEventArgument) null,
--> dvs = (vim.event.DvsEventArgument) null,
--> fullFormattedMessage = ,
--> changeTag = ,
--> eventTypeId = "esx.problem.vmfs.journal.createfailed",
--> severity = ,
--> message = ,
--> arguments = (vmodl.KeyAnyValue) [
--> (vmodl.KeyAnyValue) {
--> key = "1",
--> value = "<UUID>"
--> },
--> (vmodl.KeyAnyValue) {
--> key = "2",
--> value = "Datastore Name"
--> }
--> ],
--> objectId = "ha-host",
--> objectType = "vim.HostSystem",
--> objectName = ,
--> fault = (vmodl.MethodFault) null
--> }

YYYY-MM-DDTHH:MM:SS.618Z info hostd[13DC1B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 5504 : No space for journal on volume <UUID> (Datastore Name). Volume will remain in read-only metadata mode with limited write support until journal can be created.

Purpose

To address VM power On issues on VMFS6 datastores.

Cause

This issue is only observed on VMFS6 Filesystem in the case of storage connectivity problems while closing volume.

The journal block leaks happen on VMFS Filesystem in the case of storage connectivity problems while closing volume.

Impact / Risks

We need to shutdown the VMs in the production environment.

Resolution

This issue is resolved in VMware vSphere ESXi 6.5 Patch release ESXi650-202007001 available at Customer Connect Patch Downloads
This issue is resolved in VMware vSphere ESXi 6.7 Patch release ESXi670-202004002 available at Customer Connect Patch Downloads

Workaround

To workaround this issue

Storage vMotion all the VMs off the affected volume, and/or restore the VMs from the Backup. Then recreate this affected datastore

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
•
Windows 静止スナップショットの作成がエラー 0x80042413 で失敗する (67869)

KB
•
マイクロアーキテクチャ データ サンプリング (MDS) の脆弱性に対するハイパーバイザー支援ゲストの軽減策の実装（CVE-2018-12126、CVE-2018-12127、CVE-2018-12130、および CVE-2019-11091） (68024)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

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

Take Our Survey

Support Assistant