Getting Invalid LVMREC

[Vivek_3]

Hi,

Whenever i am trying to create or remove any logical volumne i am getting following error:

vgcfgbackup: Unable to read the physical volume. : No such device or address.
vgcfgbackups: Invalid LVMREC on physical volume /dev/rdsk/c6t5d3.

what does that mean? we are using this disk for our databases. is there something wrong with my physical disk?

this disk is part of one of my volume groups (vg_data1). if i run a commant like

>strings /etc/lvmtab

i see my volume group and disk.

BUT IF I RUN FOLLOWING COMMAND :

> vgdisplay -v /dev/vg_data1 |more

In the List of physical volumes for the disk c6t5d3 it says "UNAVAILABLE".

PV Name /dev/dsk/c6t5d3
PV Name /dev/dsk/c3t5d3 Alternate link
PV Status Unavailable
Total PE 2102
Free PE 0

what is really going on here i don't know. i having problem to access my database probably because of this.

Please Please some one help me.

waiting for reply.

let me know if you need some more info.

thanks

[Denver Osborn]

Does the system see that disk?

# lssf /dev/dsk/c6t5d3

look for the 'at adress' portion from the above command. If a hardware path is listed good. If it says 'at address ???' then the system doesn't see the disk.

If it shows the hardware path, use the following.

# vgchange -a y /dev/vg_data1

let us know if there's still a problem!

-denver

[James R. Ferguson]

Hi:

Start with an 'ioscan -fnC disk' and see if the disk represented by device file "/dev/dsk/c6t5d3" is "claimed".

It would appear that this disk is inoperative. You may have a loose SCSI connection.

Does /var/adm/syslog/syslog.log have any indication of failure?

You could try doing (for the appropriate volume group encompassing the disk):

# vgchange -a y /dev/vgXX

You can also try to test the ability to access the disk with:

# dd if=dev/dsk/c6t5d3 of=/dev/null count=10

...JRF...

[Bill McNAMARA_1]

You shouldn't really have got a major problem because there seems to be an alternate link defined which should have switched over.
try pvchange -x /dev/dsk/c3t5d3 to use the alternate link.

The /etc/lvmtab data is static. It's like your /etc/fstab in terms of filesystems. The mount being dynamic like the o/p of vgdisplay is.

The vgcfgbackup is run after every single vg, lv create, extend, remove, reduce command to save a copy of the lvm disk headers into file..
cd /etc/lvmconf/
and look at the vgname.conf files.

According to
: Invalid LVMREC on physical volume /dev/rdsk/c6t5d3.

The disk can be accessed which suggests may show up on an ioscan -fnkCdisk or ioscan -fnCdisk BUT that the lvm headers on the disk are corrupted.
If it doesn't show up on ioscan as CLAIMED, there is a h/w problem, either with the disk or the cable. If it's the disk, it'd make sense that the alternate link doesn't work.

You can try to use vgcfgrestore to try to replace known good lvmheaders on the disk if the problem is with LVM header corruption and then try to reactivate the vg with vgchange.

Later,
Bill

[Radhakrishnan Venkatara]

try to use vgcfgrestore to restore the vgbackups from /etc/lvmconf/vgxx.conf or any file if u have.

[Ajitkumar Rane]

Hi,

The PV status : unavaliable in vgdisplay indicates problem with the PV.
just do a pvdisplay -v /dev/dsk/c6t5d3 |grep stale and look for any stale extents.
even though ioscan may show claimed the PV status turns to unavaliable due to to many stale extents. If this is the case the reason may be write errors/bad blocks and the extents turn stale. You can try lvsync on the lvols on the disk to see id the extents return to current or check with dd and verify the disk.
Most probably you need to replace the disk.
check for scsi reset errors in syslog which will cause such problems.

Goodluck

[Manju Kampli]

Vivek,

it seems to be problem with the disk which it is compalining. Do ioscan -fn and see whehter it shows CLAIMED OR NO_HW.. if the status is NO_HW then the disk is gone.. then do diskinfo on that disk and make sure it returns the correct size.
you can also try doing "dd" from the disk to make sure it is 100% OK.

if the above two things are OK .. then the H/W part is OK .. then try to do vgcfgrestore on to that disk. This will restore the LVM info on to that disk.

Hope this helps,
Manju