- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - VMware
- >
- Re: 5-6 seconds timeout (scsi_cmd/nmp errors) in E...
Operating System - VMware
1752782
Members
5807
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2011 12:08 AM
03-28-2011 12:08 AM
5-6 seconds timeout (scsi_cmd/nmp errors) in ESXi 4.1 host and guests (BL460g6)
Hi all.
We're having strange timeouts in our Linux guests (Ubuntu 10.04 x86_64). A simple "df -h", or saving a file in vim, takes (not always) 5 seconds to execute. The machine continues being responsive (I can write characteres and they appear on the terminal, but I must wait for the prev command to execute).
I've executed a simple "df" in the host machine (Blade BL460g6 with ESXi 4.1u1 with only 2 RAID1 local disks), and it also takes (sometimes) the same 5-6 seconds to execute it. Those messages appear in /var/log/messages:
Mar 28 08:23:25 vmkernel: 19:17:32:35.454 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf226d40) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:25 vmkernel: 19:17:32:35.454 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf244940) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:26 vmkernel: 19:17:32:36.446 cpu1:4468)WARNING: NMP: nmpDeviceAttemptFailover: Retry world failover device "naa.600508b1001030383632343834301100"
- issuing command 0x4102bfa0a740
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmpCompleteRetryForPath: Retry world recovered device "naa.600508b1001030383632343834301100"
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)scsi_cmd_alloc returned NULL!
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)scsi_cmd_alloc returned NULL!
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)scsi_cmd_alloc returned NULL!
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)scsi_cmd_alloc returned NULL!
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bfa7e140) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)WARNING: NMP: nmp_DeviceRetryCommand: Device "naa.600508b1001030383632343834301100": awaiting fast path sta
te update for failover with I/O blocked. No prior reservation exists on the device.
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf246140) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf2a0c40) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf2ca140) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:27 vmkernel: 19:17:32:37.446 cpu1:4468)WARNING: NMP: nmpDeviceAttemptFailover: Retry world failover device "naa.600508b1001030383632343834301100"
- issuing command 0x4102bfa7e140
Mar 28 08:23:27 vmkernel: 19:17:32:37.454 cpu0:4112)NMP: nmpCompleteRetryForPath: Retry world recovered device "naa.600508b1001030383632343834301100"
(...)
We have only local RAID 1 disks (not SAN storage), and we have lots of other ESXi running perfectly...
Googling about the error talks about buying the "Battery Backed Write Caché", but we don't have it in our other ESXis and they don't present the same errors or timeouts.
Thanks for any help.
We're having strange timeouts in our Linux guests (Ubuntu 10.04 x86_64). A simple "df -h", or saving a file in vim, takes (not always) 5 seconds to execute. The machine continues being responsive (I can write characteres and they appear on the terminal, but I must wait for the prev command to execute).
I've executed a simple "df" in the host machine (Blade BL460g6 with ESXi 4.1u1 with only 2 RAID1 local disks), and it also takes (sometimes) the same 5-6 seconds to execute it. Those messages appear in /var/log/messages:
Mar 28 08:23:25 vmkernel: 19:17:32:35.454 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf226d40) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:25 vmkernel: 19:17:32:35.454 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf244940) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:26 vmkernel: 19:17:32:36.446 cpu1:4468)WARNING: NMP: nmpDeviceAttemptFailover: Retry world failover device "naa.600508b1001030383632343834301100"
- issuing command 0x4102bfa0a740
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmpCompleteRetryForPath: Retry world recovered device "naa.600508b1001030383632343834301100"
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)scsi_cmd_alloc returned NULL!
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)scsi_cmd_alloc returned NULL!
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)scsi_cmd_alloc returned NULL!
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)scsi_cmd_alloc returned NULL!
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bfa7e140) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)WARNING: NMP: nmp_DeviceRetryCommand: Device "naa.600508b1001030383632343834301100": awaiting fast path sta
te update for failover with I/O blocked. No prior reservation exists on the device.
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf246140) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf2a0c40) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:26 vmkernel: 19:17:32:36.451 cpu0:4112)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102bf2ca140) to NMP device "naa.600508b100103038363234383
4301100" failed on physical path "vmhba0:C0:T0:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0
Mar 28 08:23:47 x0 0x0 0x0.
Mar 28 08:23:27 vmkernel: 19:17:32:37.446 cpu1:4468)WARNING: NMP: nmpDeviceAttemptFailover: Retry world failover device "naa.600508b1001030383632343834301100"
- issuing command 0x4102bfa7e140
Mar 28 08:23:27 vmkernel: 19:17:32:37.454 cpu0:4112)NMP: nmpCompleteRetryForPath: Retry world recovered device "naa.600508b1001030383632343834301100"
(...)
We have only local RAID 1 disks (not SAN storage), and we have lots of other ESXi running perfectly...
Googling about the error talks about buying the "Battery Backed Write Caché", but we don't have it in our other ESXis and they don't present the same errors or timeouts.
Thanks for any help.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2011 03:09 AM
03-29-2011 03:09 AM
Re: 5-6 seconds timeout (scsi_cmd/nmp errors) in ESXi 4.1 host and guests (BL460g6)
Answering myself... (in case I can help others with the same problem).
Following [1] recommendations, we've bought and installed the Battery Backed Write Cache Module (BBWC) and the problem dissapeared:
[1] http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01832427〈=en&cc=us&taskId=135&prodSeriesId=420496&prodTypeId=18964
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP