- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- hpap pointing to non-existant physical path
Disk Enclosures
1753851
Members
7425
Online
108807
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
04-27-2009 12:12 PM
04-27-2009 12:12 PM
hpap pointing to non-existant physical path
autopath display
==================================================================
HPswsp Version : A.3.0F.02F.02F
==================================================================
Auto Discover : OFF (* we run autopath discover as and init.d script)
==================================================================
Array Type : EVA-AA
Array WWN : 5000-1FE1-5010-EBF0
Read Optimize : ON
Path Verification Period : 00:10
==================================================================
Lun WWN : 6005-08B4-000B-D231-0000-B000-0413-0000
Virtual Device File : /hpap/dsk/hpap67
Load Balancing Policy : Shortest Queue Length
Lun Timeout : Infinite Retry (-1)
==================================================================
Device Path Status
==================================================================
/dev/dsk/c45t0d1 Active
/dev/dsk/c46t0d1 Active
/dev/dsk/c47t0d1 Active
/dev/dsk/c48t0d1 Active
/dev/dsk/c49t0d1 Active
/dev/dsk/c50t0d1 Active
/dev/dsk/c51t0d1 Active
/dev/dsk/c52t0d1 Active
/dev/dsk/c55t0d1 Active
/dev/dsk/c56t0d1 Active
/dev/dsk/c57t0d1 Active
/dev/dsk/c58t0d1 Active
/dev/dsk/c59t0d1 Active
/dev/dsk/c60t0d1 Active
/dev/dsk/c61t0d1 Active
/dev/dsk/c62t0d1 Active
==================================================================
But, issuing come comands we figure out that hpap67 is not using any of those paths:
# ls -la /hpap/dsk/hpap67
brw-r----- 1 root sys 31 0x1e0100 Apr 7 16:15 /hpap/dsk/hpap67
Looking for the physical device, with those minor/major numbers, we have:
# ls -la /dev/dsk/* | grep 0x1e0100
brw-r----- 1 bin sys 31 0x1e0100 Apr 6 14:10 /dev/dsk/c30t0d1
I don't have the old list, but I assume c30txdx was the first found path by autopath discover before the change.
This machine is primarly an Oracle RAC node and for asmdisks we use "mknod" to create special files for asmdisks, so we just recreated them with the new major/minor number.
Our doubt is why did not one of the new physical paths is used automaticaly in the hpap/dsk/hpap67 (and others). And how to "recreate" the hpap devices with the correct physical paths?
Just to confirm the bahavior, a simple dd command to show the listed paths are valid.
# dd if=/hpap/dsk/hpap67 of=/tmp/testhpap bs=512 count=1
/hpap/dsk/hpap67: No such device or address
dd: cannot open /hpap/dsk/hpap67
# dd if=/dev/dsk/c30t0d1 of=/tmp/testhpap bs=512 count=1
/dev/dsk/c30t0d1: No such device or address
dd: cannot open /dev/dsk/c30t0d1
# dd if=/dev/dsk/c45t0d1 of=/tmp/testhpap bs=512 count=1
1+0 records in
1+0 records out
==================================================================
HPswsp Version : A.3.0F.02F.02F
==================================================================
Auto Discover : OFF (* we run autopath discover as and init.d script)
==================================================================
Array Type : EVA-AA
Array WWN : 5000-1FE1-5010-EBF0
Read Optimize : ON
Path Verification Period : 00:10
==================================================================
Lun WWN : 6005-08B4-000B-D231-0000-B000-0413-0000
Virtual Device File : /hpap/dsk/hpap67
Load Balancing Policy : Shortest Queue Length
Lun Timeout : Infinite Retry (-1)
==================================================================
Device Path Status
==================================================================
/dev/dsk/c45t0d1 Active
/dev/dsk/c46t0d1 Active
/dev/dsk/c47t0d1 Active
/dev/dsk/c48t0d1 Active
/dev/dsk/c49t0d1 Active
/dev/dsk/c50t0d1 Active
/dev/dsk/c51t0d1 Active
/dev/dsk/c52t0d1 Active
/dev/dsk/c55t0d1 Active
/dev/dsk/c56t0d1 Active
/dev/dsk/c57t0d1 Active
/dev/dsk/c58t0d1 Active
/dev/dsk/c59t0d1 Active
/dev/dsk/c60t0d1 Active
/dev/dsk/c61t0d1 Active
/dev/dsk/c62t0d1 Active
==================================================================
But, issuing come comands we figure out that hpap67 is not using any of those paths:
# ls -la /hpap/dsk/hpap67
brw-r----- 1 root sys 31 0x1e0100 Apr 7 16:15 /hpap/dsk/hpap67
Looking for the physical device, with those minor/major numbers, we have:
# ls -la /dev/dsk/* | grep 0x1e0100
brw-r----- 1 bin sys 31 0x1e0100 Apr 6 14:10 /dev/dsk/c30t0d1
I don't have the old list, but I assume c30txdx was the first found path by autopath discover before the change.
This machine is primarly an Oracle RAC node and for asmdisks we use "mknod" to create special files for asmdisks, so we just recreated them with the new major/minor number.
Our doubt is why did not one of the new physical paths is used automaticaly in the hpap/dsk/hpap67 (and others). And how to "recreate" the hpap devices with the correct physical paths?
Just to confirm the bahavior, a simple dd command to show the listed paths are valid.
# dd if=/hpap/dsk/hpap67 of=/tmp/testhpap bs=512 count=1
/hpap/dsk/hpap67: No such device or address
dd: cannot open /hpap/dsk/hpap67
# dd if=/dev/dsk/c30t0d1 of=/tmp/testhpap bs=512 count=1
/dev/dsk/c30t0d1: No such device or address
dd: cannot open /dev/dsk/c30t0d1
# dd if=/dev/dsk/c45t0d1 of=/tmp/testhpap bs=512 count=1
1+0 records in
1+0 records out
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