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

vSAN support for physical sector size greater than 4K with 512 logical block size (59558)

Last Updated: 11/12/2020Categories: InformationalTotal Views: 7439Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

In the /var/log/vmkernel.log file of the ESXi host, you see entries similar to:

2018-07-25T20:44:37.588Z cpu5:66850)WARNING: ScsiPath: 4395: The Physical block size "8192" reported by the path vmhba3:C0:T1:L0 is not supported.

Note: The preceding log excerpts are only examples. Date, time, block size and path name may vary depending on your environment.

Purpose

This article provides information on support regarding physical sector size that are greater than 4K.

Overview

As device vendors continue to innovate, to achieve larger capacity support within traditional 2.5 inch and 3.5 inch form factors, physical block sizes have evolved from 512 bytes to 4K and now 8K.

Devices vendors are traditionally ahead of application vendors. To bridge this transition gap, emulations likes 512 emulation (512e) are used.
This means 512 logical block size layered over a larger physical sector size. The device vendor firmware, will handle the translation from 512 bytes to 8K using the read-modify-write (R-M-W) model.
This translation is proprietary to the device vendors.

Any 512e devices with non-4K physical block size for ESXi can have performance issues as we do not optimize specifically for these devices in any way.

Impact / Risks

Performance impacts:

The R-M-W that happens during translation, may potentially add latency, depending on the efficiency of the device vendor’s firmware algorithm.

Resolution

This is a known issue affecting VMware ESXi 6.5.x and 6.7.x.

Currently, there is no resolution.

Workaround

vSAN interacts with devices based on logical block sizes; and leaves the responsibility of the R-M-W translation to the device firmware.

At VMware, we will continuously keep evaluating way of optimizing. Hence, even though, we support 8K physical sectors sizes with 512 logical block sizes, we will always review ways to optimize where possible.

This message is benign and can be safely ignored if the physical sector size is greater than 4K.

Note: Performance experience of such devices may vary as VMware is not optimized specifically for these devices in any way. These potential performance issues could be associated to the read-modify-write algorithm with the device controller; hence VMware recommends you to contact your storage vendor when you encounter device specific performance issues.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

Take Our Survey

Support Assistant