- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: lvm allert
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
тАО11-03-2006 03:35 AM
тАО11-03-2006 03:35 AM
lvm allert
vmunix: LVM: Recovered Path (device 0x1f0aa100) to PV 3 in VG 2.
vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000048cc5040), from raw device 0x1f0da100 (with priority: 1, and current flags: 0x0) to raw device 0x1f0aa100 (with priority: 0, and current flags: 0x80).
vmunix: LVM: Recovered Path (device 0x1f0aa200) to PV 4 in VG 2.
vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000048cbd840), from raw device 0x1f0da200 (with priority: 1, and current flags: 0x0) to raw device 0x1f0aa200 (with priority: 0, and current flags: 0x80).
vmunix: LVM: Recovered Path (device 0x1f0aa300) to PV 5 in VG 2.
vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000048cbd080), from raw device 0x1f0da300
couls someone let us know why it,s happening whilw i am not able to get any device related above minnor numbert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2006 03:44 AM
тАО11-03-2006 03:44 AM
Re: lvm allert
What does dmesg tell you?
Also try cstm mstm and xstm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2006 03:57 AM
тАО11-03-2006 03:57 AM
Re: lvm allert
this error occurs how much a LVM way presents imperfection, and the communication passes to be transmitted by the other fiber way. but analyzing this error we can see that he himself ja made recovery. that is ja came back to transmit for the main way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2006 06:25 AM
тАО11-03-2006 06:25 AM
Re: lvm allert
looks like your primary path to the storage fails sometimes. Once the path came back, LVM switch back from the alternate path to the primary.
You should investigate the primary path (and all the fiber cables and switches in this path).
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2006 06:48 AM
тАО11-03-2006 06:48 AM
Re: lvm allert
I've seen similar problems with MSA30s SCSI attached to HPUX.
There is a new scsi driver for HPUX that fixes the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2006 09:52 PM
тАО11-03-2006 09:52 PM
Re: lvm allert
Hello Mukesh
Check the connectivity between system and disk unit.If its ok check the disk I/O load whether too high.If its ok it seems that any of ur disk is about to fail.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2006 03:16 PM
тАО11-05-2006 03:16 PM
Re: lvm allert
The errors were due to LVM switching from its primary link to alternate link may be due to some cabling issue or maintenance.
You can see that the alternate link taking over and says Recovered.
To find the device file... use these simple steps...
1. From the log (device 0x1f0aa100)
2. Eliminate 0x1f so the minor number is 0aa100
3. cd /dev/dsk
4. ll | grep 0aa100
will give you cXtXdX
One Note: you didnot assign points to the above replys; points assignment shows the replier that the requestor has tried his solutions and how much the solution has met his request.
Regards.
Vinod
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2006 08:32 PM
тАО11-05-2006 08:32 PM
Re: lvm allert
Whats your PV TIMEOUT value. If you have default TIMEOUT value, this error may come.
If possible change your TIMEOUT value to 120 and check again.
- Vivek