make_recovery causing errors in syslog

[kenny chia]

Hi
There several SCSI reset messages written to the syslog file while performing a make_recovery.

My first guess is that this is caused by a problem tape. But upon close examination of the syslog entries I noticed the following messages

Jun 2 15:14:36 h vmunix: LVM: PV 0 has been returned to vg[0].
Jun 2 15:14:36 h vmunix: LVM: PV 1 has been returned to vg[0].
Jun 2 15:14:49 h LVM[13122]: Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
Jun 2 15:14:49 h LVM[13122]: /usr/sbin/vgcfgbackup vg00
Jun 2 15:14:49 h LVM[13124]: Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf
Jun 2 15:14:49 h LVM[13124]: /usr/sbin/vgcfgbackup vg01
Jun 2 15:14:49 h LVM[13126]: /usr/sbin/vgexport -p -m /etc/lvmconf/vg01.mapfile vg01

Anything serious here? The attachment contains the full details

[Michael Tully]

This is not necessarily a problem. It could be only a timeout issue, but having the diagnostics disabled does not help us analyse this. Make_recovery does scan your hardware.

Do you have the latest ignite software? If not get it here: http://www.software.hp.com/products/IUX/download.html

Try to start the diagnostics again.

# /sbin/init.d/diagnostic stop
# /sbin/init.d/diagnostic start

This posting also provides some further analysis. http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x264768c57f64d4118fee0090279cd0f9,00.html

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"

[Cheryl Griffin]

This is a timing issue with the disks.
PV 0 has been returned to vg[0] ==>
Physcial Volume 0 has been returned to Volume group 0 --> this equates to the disks in vg00
To get the disk names:
# strings /etc/lvmtab OR
# vgdisplay /dev/vg00

You can do a couple things:
1) Increase the timeout of the disk
# pvdisplay /dev/dsk/cxtxdx
Look for:
IO Timeout (Seconds)

The default is set by LVM and is 30. You can increase this with pvchange:
# pvchange -t 90 /dev/dsk/c0t5d0

2) Also make sure that you have the right SCSI patch. For instance 10.20 PHKL_16751, 11.00 PHKL_18543, etc.

Increasing the timeout should eleviate the problem.

[Cheryl Griffin]

In addition to the SCSI patch, you want to make sure you have the right LVM patches as well.