1830504 Members
2448 Online
110006 Solutions
New Discussion

Invalid MCR

 
Haitham Hamad
Regular Advisor

Invalid MCR

I replaced a faulty mirror disk in vg03. After morning reboot, dmesg is showing
LVM: vg[3] pv[1] Invalid MCR, Performing full resync
Will it be doing resyn after every vg activation
6 REPLIES 6
Christopher McCray_1
Honored Contributor

Re: Invalid MCR

Hello,

I belive it does, but since the disks are synced on the way down (reboot), it shouldn't take very long at all.

Hope this helps

Chris
It wasn't me!!!!
Haitham Hamad
Regular Advisor

Re: Invalid MCR

Is there a way to fix this problem and clear the dmesg
Christopher McCray_1
Honored Contributor

Re: Invalid MCR

Hello again,

When you replaced the disk, did you perform and vgcfgrestore on it and a vgsync?

Can you post the output of vgdisplay -v vg03?

Thanks

Chris
It wasn't me!!!!
Haitham Hamad
Regular Advisor

Re: Invalid MCR

After I replace the disk, I did the vgcfgrestore, vgchange, and vgsync. Here is the vgdisplay./dev/dsk/c1t11d0 was the failed disk
--- Volume groups ---
VG Name /dev/vg03
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 3
Open LV 3
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 2171
VGDA 4
PE Size (Mbytes) 4
Total PE 4340
Alloc PE 2400
Free PE 1940
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg03/lvol2
LV Status available/syncd
LV Size (Mbytes) 1000
Current LE 250
Allocated PE 500
Used PV 2

LV Name /dev/vg03/lvol3
LV Status available/syncd
LV Size (Mbytes) 1000
Current LE 250
Allocated PE 500
Used PV 2

LV Name /dev/vg03/lvol4
LV Status available/syncd
LV Size (Mbytes) 2800
Current LE 700
Allocated PE 1400
Used PV 2


--- Physical volumes ---
PV Name /dev/dsk/c0t10d0
PV Status available
Total PE 2170
Free PE 970

PV Name /dev/dsk/c1t11d0
PV Status available
Total PE 2170
Free PE 970
James R. Ferguson
Acclaimed Contributor

Re: Invalid MCR

HI:

The 'dmesg' buffer is small and circular. Messages are not purged but overwritten as space is needed. The 'vgdiaplay' you posted indicates that all logical volumes have been resynchronized. The "Invalid MCR" message reflected the situation where there was an invalid "Mirror Consistency Record" and a 'vgsync' was necessary.

You should also find this message in your 'var/adm/syslog/syslog.log'.

Regards!

...JRF...
Haitham Hamad
Regular Advisor

Re: Invalid MCR

another reboot cleared the dmesg. thanks everyone