- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Unexpected Path-failover failure
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО09-05-2005 09:37 PM
тАО09-05-2005 09:37 PM
Unexpected Path-failover failure
I hope someone can shed some light on the following. During a storage migration exercise on EMC Symmetrix, we experienced a failure situation, and we recreated this problem in a lab environment:
- We had 4 paths configured to a device, and "hwmgr тАУshow scsi тАУfull" for the device showed all 4 paths as valid.
- Next we started running an I/O generator to this device, using "dt".
- Then on the EMC side, two of the paths were "write disabled". The write disabling of the channels was done by creating a device group and using the "symld -g xxx -SA x -p x write_disable" command.
- This resulted in "SCSI events" being reported in the system log, and "A change has occurred in an error counter for device (HWID=XXX lid=4)" message for the device.
- The I/O generator crashed with "dt: 'write', errno = 5 - I/O error"
- However, "hwmgr тАУshow scsi тАУfull" still showed the 4 paths as "valid".
- Trying to start the I/O generator again failed with the same "write I/O" error.
- Retrying these last two commands after some delay still gives the same result.
We did find that using тАЬre-zoningтАЭ on the EMC side does provide the path-failover required. However why do we see the behavior described above on Tru64?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2005 01:03 AM
тАО09-06-2005 01:03 AM
Re: Unexpected Path-failover failure
When you use rezoning, the luns are not visible any more and then a "failover" is needed to maintain access.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2005 09:46 PM
тАО09-08-2005 09:46 PM
Re: Unexpected Path-failover failure
This is the simple answer. Just don't do this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2005 11:21 PM
тАО09-08-2005 11:21 PM
Re: Unexpected Path-failover failure
Yup we found out the hard way "not to do this" :-)
Is it possible to disable a specific path from the OS side?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2005 11:27 PM
тАО09-08-2005 11:27 PM