- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: What is going on here...
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
тАО07-19-2004 03:31 AM
тАО07-19-2004 03:31 AM
They appear to be fixed but I wanted some clarification from you guys... I know quite a bit about LVM Stuff but this is greek to me.
Jul 18 06:16:11 chpcfas3 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x
00000000586a9800), from raw device 0x1f0d0700 (with priority: 0, and current fla
gs: 0x40) to raw device 0x1f120700 (with priority: 1, and current flags: 0x0).
Jul 18 06:16:11 chpcfas3 vmunix:
Jul 18 06:16:11 chpcfas3 vmunix: SCSI: Read error -- dev: b 31 0x0d0700, errno:126, resid: 2048,
Jul 18 06:16:11 chpcfas3 vmunix: blkno: 8, sectno: 16, offset: 8192, bcou
nt: 2048.
Jul 18 06:16:19 chpcfas3 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x
00000000586f5080), from raw device 0x1f0d1000 (with priority: 0, and current flags: 0x40) to raw device 0x1f121000 (with priority: 1, and current flags: 0x0).
Jul 18 06:16:19 chpcfas3 vmunix: LVM: vg[3]: pvnum=0 (dev_t=0x1f120700) is POWERFAILED
Jul 18 06:16:19 chpcfas3 vmunix: LVM: vg[3]: pvnum=1 (dev_t=0x1f121000) is POWERFAILED
Jul 18 06:16:19 chpcfas3 vmunix: LVM: Restored PV 1 to VG 3.
Jul 18 06:16:37 chpcfas3 vmunix: LVM: Path (device 0x1f0d1100) to PV 0 in VG 4 Failed!
Jul 18 06:16:19 chpcfas3 vmunix: LVM: vg[3]: pvnum=0 (dev_t=0x1f120700) is POWERFAILED
Jul 18 06:16:37 chpcfas3 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x
000000005893b080), from raw device 0x1f0d1100 (with priority: 0, and current flags: 0x40) to raw device 0x1f121100 (with priority: 1, and current flags: 0x0).
Jul 18 06:16:37 chpcfas3 vmunix: LVM: vg[4]: pvnum=0 (dev_t=0x1f121100) is POWERFAILED
Jul 18 06:16:42 chpcfas3 vmunix: LVM: Recovered Path (device 0x1f120700) to PV 0 in VG 3.
Jul 18 06:16:42 chpcfas3 vmunix: LVM: Restored PV 0 to VG 3.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2004 03:36 AM
тАО07-19-2004 03:36 AM
SolutionYou're getting errors from disk devices
c13t0d7
c13t1d0
c18t0d7
c18t1d0
c13t1d1
c18t1d1
to be exact.
I suspect a timeout issue on the c13 channel & it switches over to th alt c18 path.
You probably need to increase the timeout value from the default 30 seconds
Use either pvchange -t or lvchange -t
HTH,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2004 03:42 AM
тАО07-19-2004 03:42 AM
Re: What is going on here...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2004 03:46 AM
тАО07-19-2004 03:46 AM
Re: What is going on here...
It looked as though it corrected the errors, I just wanted to know what was going on.
I will have a look at the diags.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2004 03:47 AM
тАО07-19-2004 03:47 AM
Re: What is going on here...
1. A PV changed to claternate path.
2. The disk power failed. Stopped spinning and has problems.
Now which disks??
ll /dev/dsk/*|egrep "0x1f12|0x1f0d1"
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2004 03:54 AM
тАО07-19-2004 03:54 AM
Re: What is going on here...
I had another server had the same problem at the exact same time... within a minute or so.
Now these disks are connected from a SAN to these servers.
I will go over them with my HP CE...
Thanks all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2004 03:58 AM
тАО07-19-2004 03:58 AM
Re: What is going on here...
e.g 0x1f0d0700
The first 2 hex digits (1fhex - 31decimal) indicate the major device number. Do an lsdev and look for "31". You will find that major block device 31 is SCSI disk. Thus this is a /dev/dsk device node.
The next 2 hex digits (0dhex - 13 decimal) indicate the bus "instance" number or controller number; "c13" in this case.
The next hex digit (0) indicates the SCSI ID or target. "t0" in this case.
The next hex digit (7) indicates the LUN (d7) in this case.
The remaining 2 hex digits are device driver specific.
In summary, 0x1f0d0700 decodes to
/dev/dsk/c13t0d7.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2004 06:09 AM
тАО07-19-2004 06:09 AM
Re: What is going on here...
So now harm done.
PS:
OOPSIE!!!!
Seems I had two posts on this sorry... the website was hanging and I killed my sesssion and restarted IE...and did a second one without looking...
Pleae dont delete either as both have suggestions that might help others.