Operating System - HP-UX
1832998 Members
2409 Online
110048 Solutions
New Discussion

LVM Error in dmesg command

 
SOLVED
Go to solution
Michael Schon
Advisor

LVM Error in dmesg command

The output of the dmesg command is showing some disk problem. I have checked the syslog, nothing is showing up there. I have checked the ioscan, all disks seem to be CLAIMED there. I have checked the vgdisplay, nothing seems to be stale or Unavailable there.

Can any one please help me in this regard.

Here is the dmesg output:
# dmesg

Jun 30 17:15
...
erformed a switch for Lun ID = 0 (pv = 0x000000004b1a8000), from raw device 0x1f331400 (with priority: 0, and current flags: 0x0) to raw device 0x1f1f1400 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b1a8000), from raw device 0x1f1f1400 (with priority: 0, and current flags: 0x0) to raw device 0x1f281400 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b1a8000), from raw device 0x1f281400 (with priority: 0, and current flags: 0x0) to raw device 0x4019000 (with priority: 1, and current flags: 0x100).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b51e000), from raw device 0x1f3d0200 (with priority: 0, and current flags: 0x0) to raw device 0x1f350200 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b51e000), from raw device 0x1f350200 (with priority: 0, and current flags: 0x0) to raw device 0x1f210200 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b51e000), from raw device 0x1f210200 (with priority: 0, and current flags: 0x0) to raw device 0x1f2a0200 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b51e000), from raw device 0x1f2a0200 (with priority: 0, and current flags: 0x0) to raw device 0x4010000 (with priority: 1, and current flags: 0x100).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b290000), from raw device 0x1f3e0100 (with priority: 0, and current flags: 0x0) to raw device 0x1f360100 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b290000), from raw device 0x1f360100 (with priority: 0, and current flags: 0x0) to raw device 0x1f220100 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b290000), from raw device 0x1f220100 (with priority: 0, and current flags: 0x0) to raw device 0x1f2b0100 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b290000), from raw device 0x1f2b0100 (with priority: 0, and current flags: 0x0) to raw device 0x4007000 (with priority: 1, and current flags: 0x100).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b2b0000), from raw device 0x1f3e2500 (with priority: 0, and current flags: 0x0) to raw device 0x1f362500 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b2b0000), from raw device 0x1f362500 (with priority: 0, and current flags: 0x0) to raw device 0x1f222500 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b2b0000), from raw device 0x1f222500 (with priority: 0, and current flags: 0x0) to raw device 0x1f2b2500 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b2b0000), from raw device 0x1f2b2500 (with priority: 0, and current flags: 0x0) to raw device 0x4006000 (with priority: 1, and current flags: 0x100).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004bb04000), from raw device 0x1f3f0100 (with priority: 0, and current flags: 0x0) to raw device 0x1f370100 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004bb04000), from raw device 0x1f370100 (with priority: 0, and current flags: 0x0) to raw device 0x1f230100 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004bb04000), from raw device 0x1f230100 (with priority: 0, and current flags: 0x0) to raw device 0x1f2c0100 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004bb04000), from raw device 0x1f2c0100 (with priority: 0, and current flags: 0x0) to raw device 0x4003000 (with priority: 1, and current flags: 0x100).
NOTICE: Succesfully get server pgid : 7615

NOTICE: Succesfully get server pgid : 7615

This output from ps to PID 7615:
# ps -ef |grep 7615
root 7615 1 0 May 28 ? 795:26 /sbin/sddsrv
5 REPLIES 5
James R. Ferguson
Acclaimed Contributor
Solution

Re: LVM Error in dmesg command

Hi:

If the current 'syslog' doesn't show the message, the 'dmesg' buffer is old.

That said, the messages indicate that a LVM alternate link switch (primary link to secondary) occured.

Regards!

...JRF...
Steven E. Protter
Exalted Contributor

Re: LVM Error in dmesg command

Shalom,

Looks like the system has trouble with two disks or:

There are two paths and pvlink configuration is in place and switching back and forth between disks.

This could indicate a problem with the media, scsi or fiber.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Nido
Trusted Contributor

Re: LVM Error in dmesg command

Hi Michael,

These are informational messages about PV link switch. Check the /var/adm/syslog/syslog.log for the current status.

>>>>I have checked the vgdisplay, nothing seems to be stale or Unavailable there.
If everything looks good, then no worry.


Cheers!!

" Let Villagers Be Happy!! "
Michael Schon
Advisor

Re: LVM Error in dmesg command

Thanks for all!

They were old.

Michael
Michael Schon
Advisor

Re: LVM Error in dmesg command

Thanks all