topic Re: LVM error messages in Operating System - HP-UX

LVM error messages

ln_unix — Mon, 03 May 2010 08:20:58 GMT

Hello All,

I am getting following messages in syslog.log,,,,can anyone please explain meaning of below messages????

May 3 09:00:30 abcd vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000048248000), from raw device 0x1f0a1400 (with priority: 0, and current fla
gs: 0x0) to raw device 0x1f0c1400 (with priority: 1, and current flags: 0x0).
May 3 09:00:30 abcd vmunix: LVM: VG 64 0x010000: Flushing the deferred attach list.
May 3 09:00:30 abcd LVM[4753]: vgreduce vgabcd /dev/dsk/c10t1d4 /dev/dsk/c12t1d4
May 3 09:00:31 abcd LVM[4753]: Volume Group configuration for /dev/vgabcd has been saved in /etc/lvmconf/vgabcd.conf

Thanks in advance for your help and support...

Best Regards,
LN

Re: LVM error messages

HP-UX_Ali — Mon, 03 May 2010 08:40:57 GMT

HI

It seems your alternate link is getting disconecting and thus updating /etc/lvmconf/vgabcd.conf.
Is this message coming continously ?
have you seen alternate link through vgdisplay..

If you provide the output.. that can give clear picture.

Thanks

Re: LVM error messages

Michal Kapalka (mikap) — Mon, 03 May 2010 08:40:58 GMT

hi,

if you have alternate link in the VG-s,
and the primary will fail ...., them the alternate link will used.

check the availability of all components disk/HBA ....

ioscan -fn |grep NO_HW

grep EMS /var/adm/syslog/syslog.log

mikap

Re: LVM error messages

Torsten. — Mon, 03 May 2010 11:03:41 GMT

A vgreduce is always user caused.

Somebody was modifying your LVM configuration.

.

Re: LVM error messages

singh sanjeev — Mon, 03 May 2010 11:58:13 GMT

someone has done some LVM configuration change ,as syslog show disk has been removed from the vg*. alert are due to vgreduce.

Re: LVM error messages

TTr — Mon, 03 May 2010 18:27:13 GMT

Not only someone modified the LVM configuration as Torsten said, but they vgreduced the primary path first. That's why the server performed a switch from one raw device (primary path) to another (alternate path). But then the alternate path (which now bacame the only/primary path) was vgreduced as well. So if the vgreduce was intentional, the path switching is normal.

0x1f0a1400 is /dev/dsk/c10t1d4

0x1f0c1400 is /dev/dsk/c12t1d4

When you vgreduce disk in the future you should be vgreducing the alternate paths first and then vgreduce the primary path. You can do it in the same command or two different commands.

vgreduce vgabcd /dev/dsk/c12t1d4 /dev/dsk/c10t1d4

or

vgreduce vgabcd /dev/dsk/c12t1d4 (alt)
vgreduce vgabcd /dev/dsk/c10t1d4 (pri)

Re: LVM error messages

HP-UX_Ali — Thu, 06 May 2010 06:17:45 GMT

dear in_unix

Kindly assign point if you have recieved your solution.. :) ....

Else people just waiting time in giving solutions.