HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- powerpath 4.5.0 hpux write error
Operating System - HP-UX
1836970
Members
2506
Online
110111
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
Forums
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
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-20-2006 12:56 AM
03-20-2006 12:56 AM
powerpath 4.5.0 hpux write error
Hi,
At the moment we're upgraden our naviagent and
powerpath-software on HPUX 11.0
Naviagent from 6.7.0.4.7 to 6.19.1.3.0
Powerpath from 4.1.0 to 4.5.0
I've a host with 2 fibre-cards and 2 zonings :
HBA0 --> SPA CX600
HBA1 --> SPB CX600
All the luns have default : SPB
When I remove this zoning, everything looks ok
but I see 'strange' loggings, any idea ?
"SCSI: Async write error -- dev: b 31 0x060000, errno: 126, resid: 8192,
blkno: 26725448, sectno: 53450896, offset: 1597054976, bcount: 8192.
SCSI: Async write error -- dev: b 31 0x060000, errno: 126, resid: 8192,
blkno: 26645311, sectno: 53290622, offset: 1514994688, bcount: 8192.
SCSI: Async write error -- dev: b 31 0x060000, errno: 126, resid: 8192,
blkno: 20841664, sectno: 41683328, offset: -132972544, bcount: 8192.
SCSI: Read error -- dev: b 31 0x060000, errno: 126, resid: 8192,
blkno: 2442000, sectno: 4884000, offset: -1794359296, bcount: 8192.
SCSI: Write error -- dev: b 31 0x060000, errno: 126, resid: 1024,
blkno: 26615816, sectno: 53231632, offset: 1484791808, bcount: 1024.
emcp:Mpc:Error: Path c6t0d0 to CK200033400079 is dead.
emcp:Mpc:Error: Killing bus 6 to CLARiiON CK200033400079 port B0.
emcp:Mpc:Info: Trespassed volume 6006016F930D00006FB5E379F440D811 to SPA
Mar 20 14:40
emcp:Mpc:Info: Path c6t0d0 to CK200033400079 is alive.
emcp:Mpc:Info: Restored volume 6006016F930D00006FB5E379F440D811 to: default SPB "
tx
At the moment we're upgraden our naviagent and
powerpath-software on HPUX 11.0
Naviagent from 6.7.0.4.7 to 6.19.1.3.0
Powerpath from 4.1.0 to 4.5.0
I've a host with 2 fibre-cards and 2 zonings :
HBA0 --> SPA CX600
HBA1 --> SPB CX600
All the luns have default : SPB
When I remove this zoning, everything looks ok
but I see 'strange' loggings, any idea ?
"SCSI: Async write error -- dev: b 31 0x060000, errno: 126, resid: 8192,
blkno: 26725448, sectno: 53450896, offset: 1597054976, bcount: 8192.
SCSI: Async write error -- dev: b 31 0x060000, errno: 126, resid: 8192,
blkno: 26645311, sectno: 53290622, offset: 1514994688, bcount: 8192.
SCSI: Async write error -- dev: b 31 0x060000, errno: 126, resid: 8192,
blkno: 20841664, sectno: 41683328, offset: -132972544, bcount: 8192.
SCSI: Read error -- dev: b 31 0x060000, errno: 126, resid: 8192,
blkno: 2442000, sectno: 4884000, offset: -1794359296, bcount: 8192.
SCSI: Write error -- dev: b 31 0x060000, errno: 126, resid: 1024,
blkno: 26615816, sectno: 53231632, offset: 1484791808, bcount: 1024.
emcp:Mpc:Error: Path c6t0d0 to CK200033400079 is dead.
emcp:Mpc:Error: Killing bus 6 to CLARiiON CK200033400079 port B0.
emcp:Mpc:Info: Trespassed volume 6006016F930D00006FB5E379F440D811 to SPA
Mar 20 14:40
emcp:Mpc:Info: Path c6t0d0 to CK200033400079 is alive.
emcp:Mpc:Info: Restored volume 6006016F930D00006FB5E379F440D811 to: default SPB "
tx
I have a vision...... a television
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2006 01:03 AM
03-20-2006 01:03 AM
Re: powerpath 4.5.0 hpux write error
Shalom tx,
Check the world wide name (WWN) on the zoning configuration.
SEP
Check the world wide name (WWN) on the zoning configuration.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2006 01:09 AM
03-20-2006 01:09 AM
Re: powerpath 4.5.0 hpux write error
The zonings are ok.
The luns are visisble through 2 paths.
I'm just testing that the powerpath-soft is
working ok.
I'm worried about the read/write errors.
The luns are visisble through 2 paths.
I'm just testing that the powerpath-soft is
working ok.
I'm worried about the read/write errors.
I have a vision...... a television
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2006 12:11 PM
03-25-2006 12:11 PM
Re: powerpath 4.5.0 hpux write error
Hi Gerrit,
If luns are tresspassing continously from SPA to SPB you should stop this happening. check for the basic setting like "Failover mode", "array comm path" and most important "Initiator type".
Regards
Sathish
If luns are tresspassing continously from SPA to SPB you should stop this happening. check for the basic setting like "Failover mode", "array comm path" and most important "Initiator type".
Regards
Sathish
Don't Think too much
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP