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

ESXi Host with EMC RecoverPoint Installed may PSOD during shutdown (75056)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

ESXi host running EMC RecoverPoint IO filter daemon may PSOD during shutdown

VIB Name: RP-Splitter RPESX-00.5.2.2.0.0.m.128.000 EMC_Recoverpoint

Backtrace shows similar entries

2019-08-12T14:30:42.139Z cpu0:2097309)World: 3015: PRDA 0x418040000000 ss 0x0 ds 0xfd0 es 0xfd0 fs 0xfd0 gs 0xfd0
2019-08-12T14:30:42.139Z cpu0:2097309)World: 3017: TR 0xfd8 GDT 0x4509c4200000 (0xfe7) IDT 0x41801a965000 (0xfff)
2019-08-12T14:30:42.139Z cpu0:2097309)World: 3018: CR0 0x8001003d CR3 0x3f85000 CR4 0x10216c
2019-08-12T14:30:42.186Z cpu0:2097309)Backtrace for current CPU #0, worldID=2097309, fp=0x417fdabb9320
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9beb0:[0x41801a863465]FDS_CloseDevice@vmkernel#nover+0x9 stack: 0x417fdabb9320, 0x41801b73f84c, 0x4301073a5160, 0x41801b72f069, 0x43065da875b8
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bed0:[0x41801b73f84b]FS3_RebootCleanup@esx#nover+0x7c stack: 0x43065da875b8, 0x41801a90e5ed, 0x0, 0x1, 0x3
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bee0:[0x41801b72f068]FS3RebootHandler@esx#nover+0x5d stack: 0x0, 0x1, 0x3, 0x41801a8ed9ce, 0x43065da87070
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bef0:[0x41801a90e5ec]Reboot_RunHandlers@vmkernel#nover+0x41 stack: 0x3, 0x41801a8ed9ce, 0x43065da87070, 0x31a6a222dd9, 0x43065da87570
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bf10:[0x41801a8ed9cd]Init_VMKernelShutdownHelper@vmkernel#nover+0x2de stack: 0x43065da87570, 0x41801a8eb1f3, 0x43065da87088, 0x0, 0x43065da870b8
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bf30:[0x41801a8eb1f2]HelperQueueFunc@vmkernel#nover+0x30f stack: 0x43065da870b8, 0x43065da870a8, 0x43065da870e0, 0x451a44ea3000, 0x43065da870b8
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bfe0:[0x41801ab0e322]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0, 0x0, 0x0, 0x0, 0x0
2019-08-12T14:30:42.208Z cpu0:2097309)

VMware ESXi 6.7.0 [Releasebuild-13981272 x86_64]
2019-08-12T14:30:42.210Z cpu0:2097309)@BlueScreen: #PF Exception 14 in world 2097309:HELPER_MISC_ IP 0x41801a863465 addr 0x18PTEs:0x0;
2019-08-12T14:30:42.210Z cpu0:2097309)Code start: 0x41801a800000 VMK uptime: 0:00:28:52.427
2019-08-12T14:30:42.211Z cpu0:2097309)0x451a44e9beb0:[0x41801a863465]FDS_CloseDevice@vmkernel#nover+0x9 stack: 0x417fdabb9320
2019-08-12T14:30:42.211Z cpu0:2097309)0x451a44e9bed0:[0x41801b73f84b]FS3_RebootCleanup@esx#nover+0x7c stack: 0x43065da875b8
2019-08-12T14:30:42.211Z cpu0:2097309)0x451a44e9bee0:[0x41801b72f068]FS3RebootHandler@esx#nover+0x5d stack: 0x0
2019-08-12T14:30:42.212Z cpu0:2097309)0x451a44e9bef0:[0x41801a90e5ec]Reboot_RunHandlers@vmkernel#nover+0x41 stack: 0x3
2019-08-12T14:30:42.212Z cpu0:2097309)0x451a44e9bf10:[0x41801a8ed9cd]Init_VMKernelShutdownHelper@vmkernel#nover+0x2de stack: 0x43065da87570
2019-08-12T14:30:42.213Z cpu0:2097309)0x451a44e9bf30:[0x41801a8eb1f2]HelperQueueFunc@vmkernel#nover+0x30f stack: 0x43065da870b8
2019-08-12T14:30:42.213Z cpu0:2097309)0x451a44e9bfe0:[0x41801ab0e322]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0
2019-08-12T14:30:42.217Z cpu0:2097309)base fs=0x0 gs=0x418040000000 Kgs=0x0

Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.

Cause

There is a race between volume open and shutdown. The volume open is triggered by an splitterThread
splitterThread should not open volumes in the shutdown path.

Resolution

This is not a VMware issue.
For further information please contact DellEMC Recover Point .

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
任意のノードで Docker サービスを再起動すると、サービスの状態が健全でなく、デプロイが失敗する (75183)

Result 1 of 1

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

Take Our Survey

Support Assistant