- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Emlex HBA message :- Warning, ring[0].hash[0] iocb...
Operating System - Tru64 Unix
1748275
Members
3980
Online
108761
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
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
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
тАО08-13-2009 10:12 PM
тАО08-13-2009 10:12 PM
Emlex HBA message :- Warning, ring[0].hash[0] iocbhdr
Hi,
I have emulex FC HBAs in my Alpha servers with Tru64UNIX v5.1B. From time to time I get the following messages:-
Aug 4 15:56:48 vmunix: EMX[0]: Warning, ring[0].hash[0] iocbhdr 0xfffffc01419aac88 stalled for 65 seconds!
Aug 4 15:56:48 vmunix: ccb 0xfffffc01419aae78 0/20
Aug 4 15:56:48 vmunix: EMX[0]: Warning, ring[0].hash[1] iocbhdr 0xfffffc015ef33708 stalled for 65 seconds!
Aug 4 15:56:48 vmunix: ccb 0xfffffc015ef338f8 0/30
If anyone can let me know what would be causing this it would be greatly appreciated.
Thanks
Andrew
I have emulex FC HBAs in my Alpha servers with Tru64UNIX v5.1B. From time to time I get the following messages:-
Aug 4 15:56:48 vmunix: EMX[0]: Warning, ring[0].hash[0] iocbhdr 0xfffffc01419aac88 stalled for 65 seconds!
Aug 4 15:56:48 vmunix: ccb 0xfffffc01419aae78 0/20
Aug 4 15:56:48 vmunix: EMX[0]: Warning, ring[0].hash[1] iocbhdr 0xfffffc015ef33708 stalled for 65 seconds!
Aug 4 15:56:48 vmunix: ccb 0xfffffc015ef338f8 0/30
If anyone can let me know what would be causing this it would be greatly appreciated.
Thanks
Andrew
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2009 05:44 PM
тАО08-14-2009 05:44 PM
Re: Emlex HBA message :- Warning, ring[0].hash[0] iocbhdr
These are informative messages that were introduced in V5.1B-4 to indicate when FC disk I/O is backing up. If it happens at consistent times (such as during filesystem backups) it could just be a transient condition indicating extremely heavy I/O. Alternatively, it could indicate a problem somewhere in the I/O subsystem. You could check the error log to see if anything was logged around the same time.
Martin
Martin
I work for HPE
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2009 08:38 PM
тАО09-15-2009 08:38 PM
Re: Emlex HBA message :- Warning, ring[0].hash[0] iocbhdr
As previously indicated, these are warnings... until it starts complaining about errors.
Note tat there was a hole in the logic that was corrected in later versions of the driver concerning tape io. Normal disk io has a 60 second timeout and a lot of tape io has several minute to 90 minute timeout -- but some tape io has < 250 second timeout.
The stall config limit is set at 60 seconds I think, but if tape io has a 80 second timeout and it takes 75 seconds to complete the io then the driver will issue warnings about stalled io when there really isn't any.
If there are no tapes on the san... worry about slow io otherwise bump the stall config warning time up to 90-120 seconds.
Note tat there was a hole in the logic that was corrected in later versions of the driver concerning tape io. Normal disk io has a 60 second timeout and a lot of tape io has several minute to 90 minute timeout -- but some tape io has < 250 second timeout.
The stall config limit is set at 60 seconds I think, but if tape io has a 80 second timeout and it takes 75 seconds to complete the io then the driver will issue warnings about stalled io when there really isn't any.
If there are no tapes on the san... worry about slow io otherwise bump the stall config warning time up to 90-120 seconds.
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