Mirroring Issue

[Ken Pannell]

I had an lvol that I had mirrored by using the lvextend -m 1 lvol pvg command. There were a total of 11 devices in the pvg. Today I split the mirrors using the lvreduce -m 0 lvol devices command. However, instead of entering 11 devices to split I only entered 10. That one device is now showing up as one of the devices in the lvol. What do I need to do to clean this up?

[Mridul Shrivastava]

Try removing that device also from lvol using lvreduce -m 0, does it give any error ??
Could you please post the lvdisplay & vgdisplay output for the affected lvol and corresponding vg.

[Kevin Wright]

can you not run lvreduce?

[DCE]

If you cannot reduce the single disk, then
re-mirror the lvol and run the lvreduce command with all 11 disks

[Marvin Strong]

does lvdisplay show that it is still mirrored?

if it is mirrored
you can try lvreduce -m 0 lvol device

if it is not mirrored are you sure those are mirrored extents.
If they are not mirrored extents you can pvmove them to another disk.

you may have to remirrror and break the mirror again.

[Ken Pannell]

I'll try to answer all responses.

When I issue the command lvreduce -m 0 lvol device I get the error "MirrorCopies parameter 0 is not smaller than existing number 0;

When I try to re-mirror back to the pvg "primary" (see attachment - pvg mirror is where the data was originally mirrored to) I get the error "Not enough free physical extents available - Logical volume could not be extended - Failure possibly caused by PVG-Strict allocation policy".

When I try ro re-mirror back to the original volumes (changing allocation from pvg-strict to strict) - lvextend -m 1 lvol devices I also get the error message "Not enough free physical extenda available. Logical Volume could not be extended. Failure possibly caused by strict allocation policy"

I've attached the lvdisplay and the vgdisplay. Notice the volume c26t14d0 is in the primary pvg which is where the data was originally, and then notice it listed in the lvdisplay.

I'm thinking I need to remirror also, but maybe to a different set of devices.

[Ken Pannell]

Here's the vgdisplay.

[Sundar_7]

Ken,

First, let me make onething clear - lvreduce doesn't split the mirror, it reduces the mirror. Meaning, you no longer have a mirror copy.

The question is not clear to me as in what the goal is but if all you want is to get the LV's PEs off of c26t14d0 then you can try this

# pvmove -n /dev/vg_mis_db/orasit /dev/dsk/c26t14d0 mirror

This should empty c26t14d0 of /dev/vg_mis_db/orasit PEs.

Sundar.

[Prasanth B]

Hi,

try using

lvreduce -k -m 0 /dev/vgxx/lvol /dev/dsk/xxx

-PB

[Ken Pannell]

I ended up blowing away the lvol, moving it to another volume group and creating it at a larger size. The old volume group limited me expanding it any bigger because of the PE size. So now everything is the way it should be.

My thanks for everyone's input.

[Ken Pannell]

See my last reply to this issue.