GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Autopath Errors
Operating System - HP-UX
1846349
Members
3508
Online
110256
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
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
Go to solution
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
06-30-2004 04:19 AM
06-30-2004 04:19 AM
I have been getting some autopath errors in my syslog, and even though they appear to have corrected themselves, I was wondering if someone could help me determine how to trace back the disk & Volume Group that was having problems. I have attached a sample from the syslog and would especially like to know how to determine how to link back "VG 34" to one on the system.
Jun 30 11:36:11 wcores10 vmunix:
Jun 30 11:36:11 wcores10 vmunix: AUTOPATH: Path 0x1f3bd100 failed! Rerouting IO to alternate path
Jun 30 11:36:11 wcores10 vmunix: LVM: Recovered Path (device 0x1f44d100) to PV 0 in VG 34.
Jun 30 11:36:16 wcores10 vmunix: LVM: Restored PV 0 to VG 34.
Jun 30 11:36:18 wcores10 vmunix: AUTOPATH: Path 0x1f3bd100 recovered
Jun 30 11:36:59 wcores10 vmunix: AUTOPATH: Path 0x1f44d100 failed! Rerouting IO to alternate path
Jun 30 11:37:00 wcores10 vmunix: LVM: Recovered Path (device 0x1f44d100) to PV 0 in VG 34.
Jun 30 11:37:00 wcores10 vmunix: LVM: Restored PV 0 to VG 34.
Jun 30 11:37:08 wcores10 vmunix: AUTOPATH: Path 0x1f44d100 recovered
Jun 30 11:37:08 wcores10 vmunix:
Jun 30 11:50:20 wcores10 vmunix:
Jun 30 11:50:20 wcores10 vmunix: AUTOPATH: Path 0x1f44d100 failed! Rerouting IO to alternate path
Jun 30 11:50:20 wcores10 vmunix: LVM: Recovered Path (device 0x1f44d100) to PV 0 in VG 34.
Jun 30 11:50:20 wcores10 vmunix: LVM: Restored PV 0 to VG 34.
Jun 30 11:50:29 wcores10 vmunix: AUTOPATH: Path 0x1f44d100 recovered
Thanks!
Jun 30 11:36:11 wcores10 vmunix:
Jun 30 11:36:11 wcores10 vmunix: AUTOPATH: Path 0x1f3bd100 failed! Rerouting IO to alternate path
Jun 30 11:36:11 wcores10 vmunix: LVM: Recovered Path (device 0x1f44d100) to PV 0 in VG 34.
Jun 30 11:36:16 wcores10 vmunix: LVM: Restored PV 0 to VG 34.
Jun 30 11:36:18 wcores10 vmunix: AUTOPATH: Path 0x1f3bd100 recovered
Jun 30 11:36:59 wcores10 vmunix: AUTOPATH: Path 0x1f44d100 failed! Rerouting IO to alternate path
Jun 30 11:37:00 wcores10 vmunix: LVM: Recovered Path (device 0x1f44d100) to PV 0 in VG 34.
Jun 30 11:37:00 wcores10 vmunix: LVM: Restored PV 0 to VG 34.
Jun 30 11:37:08 wcores10 vmunix: AUTOPATH: Path 0x1f44d100 recovered
Jun 30 11:37:08 wcores10 vmunix:
Jun 30 11:50:20 wcores10 vmunix:
Jun 30 11:50:20 wcores10 vmunix: AUTOPATH: Path 0x1f44d100 failed! Rerouting IO to alternate path
Jun 30 11:50:20 wcores10 vmunix: LVM: Recovered Path (device 0x1f44d100) to PV 0 in VG 34.
Jun 30 11:50:20 wcores10 vmunix: LVM: Restored PV 0 to VG 34.
Jun 30 11:50:29 wcores10 vmunix: AUTOPATH: Path 0x1f44d100 recovered
Thanks!
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 04:58 AM
06-30-2004 04:58 AM
Solution
Hi,
I could be wrong here but I will tell you my understanding.
Recovered Path (device 0x1f44d100) to PV 0 in VG 34.
To find the device file
# cd /dev/dsk
# ls -lrt | grep 44d100
Remove the 0x1f from the error message and grep for it.
To find out the VG, run pvdisplay on the device file you get from the above command
# pvdisplay /dev/dsk/ | grep "VG"
the VG number it refers in the message must match the minor number of the group control file of the VG
# cd /dev
# find . -name group -exec ls -lrt {} \;
Take the minor number of the group control file and convert it to decimal from hex and you will get the VG number displayed in the error message.
Hope this helps
I could be wrong here but I will tell you my understanding.
Recovered Path (device 0x1f44d100) to PV 0 in VG 34.
To find the device file
# cd /dev/dsk
# ls -lrt | grep 44d100
Remove the 0x1f from the error message and grep for it.
To find out the VG, run pvdisplay on the device file you get from the above command
# pvdisplay /dev/dsk/
the VG number it refers in the message must match the minor number of the group control file of the VG
# cd /dev
# find . -name group -exec ls -lrt {} \;
Take the minor number of the group control file and convert it to decimal from hex and you will get the VG number displayed in the error message.
Hope this helps
Learn What to do ,How to do and more importantly When to do ?
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 2026 Hewlett Packard Enterprise Development LP