- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: PVLink 31 Failed! The PV is still accessible
HPE EVA Storage
1753852
Members
9124
Online
108808
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
тАО07-27-2009 03:41 PM
тАО07-27-2009 03:41 PM
PVLink 31 Failed! The PV is still accessible
Hi Guys,
I got some worriesome issues going on our servers connected to an EVA4000. We keep getting these messages everyday:
---------------------------------------------
LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000068d32000), from raw devic e 0x1f180100 (with priority: 2, and current flags: 0x0) to raw device 0x1f140100 (with priority: 0, and current flags: 0x80).
LVM: VG 64 0x010000: PVLink 31 0x140100 Recovered.
LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000068d32000), from raw devic e 0x1f140100 (with priority: 0, and current flags: 0x40) to raw device 0x1f18010 0 (with priority: 2, and current flags: 0x0).
LVM: VG 64 0x010000: PVLink 31 0x140100 Failed! The PV is still accessible.
LVM: VG 64 0x010000: PVLink 31 0x190100 Failed! The PV is still accessible.
---------------------------------------------
We are not using securepath software but only configured 'alternate links' for the VG.
And when I check the disks with ioscan and diskinfo, they all come back fine.
But still, the issue just keeps popping up and these are out production servers and we need to be sure that these errors would not cause any data corruption
So, here's hoping you guys could help me diagnose this problem and possibly resolve it.
Thanks!
I got some worriesome issues going on our servers connected to an EVA4000. We keep getting these messages everyday:
---------------------------------------------
LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000068d32000), from raw devic e 0x1f180100 (with priority: 2, and current flags: 0x0) to raw device 0x1f140100 (with priority: 0, and current flags: 0x80).
LVM: VG 64 0x010000: PVLink 31 0x140100 Recovered.
LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000068d32000), from raw devic e 0x1f140100 (with priority: 0, and current flags: 0x40) to raw device 0x1f18010 0 (with priority: 2, and current flags: 0x0).
LVM: VG 64 0x010000: PVLink 31 0x140100 Failed! The PV is still accessible.
LVM: VG 64 0x010000: PVLink 31 0x190100 Failed! The PV is still accessible.
---------------------------------------------
We are not using securepath software but only configured 'alternate links' for the VG.
And when I check the disks with ioscan and diskinfo, they all come back fine.
But still, the issue just keeps popping up and these are out production servers and we need to be sure that these errors would not cause any data corruption
So, here's hoping you guys could help me diagnose this problem and possibly resolve it.
Thanks!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2009 01:02 AM
тАО07-28-2009 01:02 AM
Re: PVLink 31 Failed! The PV is still accessible
That's c14t0d1 and c19t0d1
I suppose those will be two of the paths to the EVA. Check ioscan and see it both paths are on the same controller or the same switch.
Then check EVA or switch log.
I suppose those will be two of the paths to the EVA. Check ioscan and see it both paths are on the same controller or the same switch.
Then check EVA or switch log.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2009 11:06 PM
тАО08-06-2009 11:06 PM
Re: PVLink 31 Failed! The PV is still accessible
Hi,
I recently set the IO timeout from 60sec to 90sec. For a while, these errors went away (Feb28-Aug3), but on Aug4 it re-appeared again. This day was a high volume IO day - because of month-end processing and stuff.
What could be the next actions to take?
I recently set the IO timeout from 60sec to 90sec. For a while, these errors went away (Feb28-Aug3), but on Aug4 it re-appeared again. This day was a high volume IO day - because of month-end processing and stuff.
What could be the next actions to take?
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