LVM Error in dmesg command

Michael Schon — Tue, 30 Jun 2009 19:22:34 GMT

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

Re: LVM Error in dmesg command

James R. Ferguson — Tue, 30 Jun 2009 19:28:08 GMT

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...

Re: LVM Error in dmesg command

Steven E. Protter — Tue, 30 Jun 2009 19:40:01 GMT

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

Re: LVM Error in dmesg command

Nido — Tue, 30 Jun 2009 19:42:17 GMT

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!!

Re: LVM Error in dmesg command

Michael Schon — Tue, 30 Jun 2009 19:54:04 GMT

Thanks for all!

They were old.

Michael

Re: LVM Error in dmesg command

Michael Schon — Tue, 30 Jun 2009 19:54:46 GMT

Thanks all

topic Re: LVM Error in dmesg command in Operating System - HP-UX

LVM Error in dmesg command

Re: LVM Error in dmesg command

Re: LVM Error in dmesg command

Re: LVM Error in dmesg command

Re: LVM Error in dmesg command

Re: LVM Error in dmesg command