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

StorageRM excessive logging on ESXi 6.7 P01 and 7.0 (76733)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 13279Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

You use vSphere 6.7 or 7.0 environment

Storage I/O Control is enabled and in use

Even after patching ESXi's to 6.7 P01 or 7.0 StorageRM still has excessive logging

StorageRM logs generates more than 50 000+ lines of messages within couple of minutes

This has a huge impact on external syslog remote host

Following information on disabling SIOC logging from KB Troubleshooting Storage I/O Control (1022091) doesn't reduce the excessive logging because at level 0, it will still be printing the INFO level logs

Purpose

This article provides information on disabling SIOC logging.

Cause

These log entries are normal and occurring due to bigger Clusters reaching up to maximum of 64 ESXi hosts

Whenever storageRM updates the cluster parameters, we will have one entry per host and that is why we see a lot of logs being printed.

This function goes through the stats of all the hosts accessing that device and computes cluster wide aggregation of various stats such as iocount, latency, outstanding IOs and window sizes.

Impact / Risks

There is no impact of disabling SIOC logging. SIOC will continue to work fine and will dynamically adjust queue depths according to the data store latencies and IO limits.

Resolution

The issue is addressed in VMware ESXi 6.7 P02 and 7.0 U1. The improvements have been added to the StorageRM logging.

Workaround

You can use following to temporarily disable SIOC logging:

in file: /etc/vmsyslog.conf.d/storageRM.conf
change:
fclass = FileLoggerSyslog
to
fclass = FileLoggerNull

Please make the same change to /etc/vmsyslog.conf.d/sdrsInjector.conf

Save the files and then run
esxcli system syslog reload

This will stop storageRM and sdrsInjector logging.

NOTE: The above will only stop logging to a log file stated, however it will still send log lines to external remote syslog server. In order to completely stop excessive logging use below:

a. Edit /etc/vmware/logfilters and add the following lines:
5 | storageRM | .*
5 | sdrsInjector | .*

b. Add the line "enable_logfilters = true" to /etc/vmsyslog.conf

c. Run the command: "esxcli system syslog reload" for the configuration to take effect.

Logging should automatically stop after 5 log statements for both storageRM and sdrsInjector.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere 7.0.x

Take Our Survey

Support Assistant