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

I/Os might fail on some paths of device or datastore creation may fail if there is a flaky path (78200)

Last Updated: 3/11/2020Categories: TroubleshootingTotal Views: 5375Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

I/Os might fail on some paths of a device due to faulty switch error

Datastore creation on a device having one flaky path fails with  below error

The "Create VMFS datastore" operation failed for the entity with the following error message.
An error occurred during host configuration.
Operation failed, diagnostics report:  Unable to create Filesystem, please see VMkernel log for more details: Failed to create VMFS  on device
The vmkernel.log will report messages as below
2018-08-27T06:32:09.964Z cpu40:1001390104)NMP: nmp_ThrottleLogForDevice:3781: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL. cmdId.initiator=0x43064aecc6c0 CmdSN 0x9a
2018-08-27T06:32:09.964Z cpu40:1001390104)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.600601603b303c009271dacce40de811" state in doubt; requested fast path state update...
2018-08-27T06:32:09.964Z cpu40:1001390104)ScsiDeviceIO: SCSICompleteDeviceCommand:3294: Cmd(0x45a2ddcbd080) 0x2a, CmdSN 0x9a from world 1001393007 to dev "naa.600601603b303c009271dacce40de811" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
2018-08-27T06:32:09.976Z cpu40:1001390104)vmw_psp_rr: psp_rrCommandComplete:1972: Setting path vmhba4:C0:T1:L15 as flaky, cmd=0x45a2ddcbd080
2018-08-27T06:32:09.976Z cpu40:1001390104)vmw_psp_rr: psp_rrCommandComplete:1990: Setting eval time for path vmhba4:C0:T1:L15 as 10sec, cmd=0x45a2ddcbd080
2018-08-27T06:32:09.989Z cpu40:1001393041 opID=313e2b0b)ScsiHandle: SCSIOpenNamedDevice:752: handle=0x0x43064aecc6c0 (naa.600601603b303c009271dacce40de811 part 1) is read-only
2018-08-27T06:32:09.989Z cpu40:1001393041 opID=313e2b0b)LVM: ProbeDeviceInt:9585: Failed to detect if device <naa.600601603b303c009271dacce40de811:1> is a snapshot: Device does not contain a logical volume
2018-08-27T06:32:09.989Z cpu40:1001393041 opID=313e2b0b)LVM: InitDevice:10462: LVMProbeDevice failed on (3444138432, naa.600601603b303c009271dacce40de811:1): Device does not contain a logical volume
2018-08-27T06:32:09.989Z cpu40:1001393041 opID=313e2b0b)FSS: Create:2311: Failed to format LVM/VMFS on device 'naa.600601603b303c009271dacce40de811:1': Storage initiator error
2018-08-27T06:32:09.989Z cpu40:1001393041 opID=313e2b0b)FSS: Create:2373: Failed to create FS on dev [naa.600601603b303c009271dacce40de811:1]

The guest OS in VMs re-mount their filesystems in read-only mode or become unresponsive.

In this scenario the vmkernel.log will report FCPIO_DATA_CNT_MISMATCH .

Vmkernel.log will report message to below
2017-05-28T23:47:40.089Z cpu27:32809)<3>fnic : 2 :: hdr status = FCPIO_DATA_CNT_MISMATCH
2017-05-28T23:47:40.089Z cpu19:35295)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x28 (0x43a600ef10c0, 33236) to dev "naa.60060e80101e1970058be1670000002a" on path "vmhba2:C0:T1:L0" Failed: H:0x7 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL

Purpose

To resolve the I/O error.

Cause

If the device is claimed by PSP_RR default policy, path switching happens every 1000 IOs. Hence in case the current used path is marked as flaky, it will not switch to another working path until 1000 IOs succeed on the path.

Impact / Risks

None

Resolution

This issue is resolved in 6.7 U1 release . Refer to release notes

Workaround

To workaround this  issue use iops=1
Fore more information refer to VMware KB : Adjusting Round Robin IOPS limit from default 1000 to 1

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
起動時の /tmp のクリーンアップが原因で、Linux でのゲスト OS のカスタマイズが失敗することがある (71319)

KB
•
Intel プロセッサにおける Load Value Injection (CVE-2020-0551) の投機的実行の脆弱性に対する VMware の対応 (78194)

Results 1-2 of 2

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