Lvextend: could not re-synchonize logical volume

[AwadheshPandey]

Hello Experts,
I am getting following error when do a lvextend on a lvol,
Lvextend: could not re-synchonize stale partions of the logical volume,
I/O Error
lvextend: could not re-synchronize logical volume.

This volume group has 4 lvols and three are extended successfully, I have replaced disks, diskstatios, terminator, cable and scsi controller.
No threads link please, i had checked all of them and do a lot of work on this.

Thanks in Advance

Awadhesh

[Robert-Jan Goossens_1]

Awadesh,

How good are your Back-Up's ? How about starting with a fresh new filesystem.

Best regards,
Robert-Jan

[Arunvijai_4]

Hi Awadhesh,

Can you do a # dd if=/dev/rdsk/cxxxxxx of=/dev/null bs=1024k on the source disk ?

It could be due to bad disk.

-Arun

[HGN]

Hi

I agree with Bob if you have a good backup then you can create and new filesystem and try to sync it again.

Rgds

HGN

[A. Clay Stephenson]

Your throwing hardware at the problem essentially eliminated all chance of you recovering. You probably missed step 0 of any LVOL change. Do an lvdisplay -v for all LVOL's are make sure that all extents are "current".

[AwadheshPandey]

lvdisplay -v /dev/vgDL/lvolHome | grep -i stale produce following o/p.

00016 /dev/dsk/c2t2d0 01891 current /dev/dsk/c5t14d0 02516 stale
00199 /dev/dsk/c2t2d0 02074 current /dev/dsk/c5t14d0 02699 stale

Regards,
Awadhesh

[A. Clay Stephenson]

Yes, I know but the point is you should have done this before ever doing an lvextend. That's part of the LVM 101 curriculum.

[AwadheshPandey]

What will be impact on system if we will continue our system on this state.

Regards,

Awadhesh

[AwadheshPandey]

Clay,

Thanks for your co-operation, Let me know a proper action plan to recover this problem for initial step.

Regards,

Awadhesh

[A. Clay Stephenson]

If you are lucky then
lvsync /dev/vgDL/lvolHome

[AwadheshPandey]

Thanks Again,

lvsysnc o/p is same as above.

Regards,

Awadhesh

[A. Clay Stephenson]

At this point, you are almost certainly going to have to lvremove the LVOL and then recreate it and build a filesystem on it and restore from backup. ALWAYS run lvdisplay -v BEFORE doing any LVM operation. Before removing any disk for replacement, it is essential that all the extents on the remaining mirror be "current". Replacing a disk before doing this made recovery impossible.

[Nguyen Anh Tien]

Hi Awadhesh
To determine the cause correctly pls give me output of below commands:
#vgdisplay -v vgname --- vg contains you lv
#ioscan -fnC disk

It is suspected that PV (phisical volume- disks or lUNS) has problem!

[Mridul Shrivastava]

Awadesh,

U pls do lvreduce and remove that pv which is showing some stale extents.
Then try dd to check the disk whether it has some bad sectors.
Then extend the lv again to that pv, i hope this will sovle ur issue. Ur data will be intact.

[Devender Khatana · Accepted solution]

Hi,

The problem here is in the primary copy which is not allowing data to be read from the disk for mirroring onto the second. The solution will be to remove LVOL and recreate it on the second disk which at present have STALE PEs. Doing so will allow you to use the LVOL from one copy for time being and as soon as the faulty disk is replaced extend the mirror onto it.

Also you can have a read test on the faulty disk by

#dd if=/dev/rdsk/cxtydz of=/dev/null bs=1024K

Where /dev/rdsk/vxtydz is the disk having first copy of this LVOL not the one you are extending to.

HTH,
Devender

[singvey]

first , you should check your source volume
fsck -F vxfs|hfs -o full,nolog /xxxxx

second , you can also try this : lvcreate -l 1 -n test vg0x; lvextend -m 1 /dev/vg0x/xvolxxxx pv-path ; lvextend -L bigger-size /dev/vg0x/xvolxxxx; lvsync /dev/vg0x/xvolxxxx

[singvey]

first, you are sure that the second disk size is bigger than the source disk


you should check your source volume
fsck -F vxfs|hfs -o full,nolog /xxxxx

you can also try this : lvcreate -l 1 -n test vg0x; lvextend -m 1 /dev/vg0x/xvolxxxx pv-path ; lvextend -L bigger-size /dev/vg0x/xvolxxxx; lvsync /dev/vg0x/xvolxxxx

[AwadheshPandey]

Sorry Arun,

I accedently assign you 0 points, wating for ur post before closing this thread.

Regards,

Awadhesh

[Arunvijai_4]

Hi Awadhesh,

Here is my post :-)

-Arun

[AwadheshPandey]

Actually I want another solution rather than destroy that lvol. dd worked fine on both the disks, but there was 2 bad block entries in BBDIR of primary disk, thats why 2 PEs are in stale position, Devender,s reply very close to this problem. Thanks to All of you

Regards,

Awadhesh