Originally posted by: tony.evans

Grr, I've tried four times to post a detailed question about removing some LVM mirrors and each time, Developerworks displays an error saying 'disallowed content detected', but doesn't tell me what specifically in my post.

In summary without any examples, we removed LVM mirrors from about 50 logical volumes, 44 of them worked fine, in 6 cases (all in different VG's and on different LUNs) rmlvcopy removed the mirror from 1 of the LUNs I specified, but not the others.

I've tried to attach the description in text below which contains some examples.
#AIX-Forum

Originally posted by: SystemAdmin

Strange. Seen this problem first time, I guess for some reason ODM has not got updated correctly. I think you should try updating ODM. Also try synclvodm command that might do the trick.
#AIX-Forum

Originally posted by: tony.evans

Which bit of the ODM would you think was affecting where mirrored copies were removed with an rmlvcopy?

The ODM / VGDA clearly knew where the mirrored copies were, because on inspection it listed them correctly on all the LUNs. Also, it didn't moan when I told it which disks to remove from.

How would a synclvodm after the fact make any difference?
#AIX-Forum

Originally posted by: SystemAdmin

Now that the mirror break is done, here are two quick ways that you could use to push the PPs around (using your example disks/lv):

1) Use 'migratepv' to move the content from one drive to another, like:

migratepv vpath49 vpath36

This command will likely fill in towards the head of the disk, and may change the position of the PPs on the new disk relative to the old disk. This might matter, it might not. If it does matter, you can do a little more leg (or script) work and use...

2) the 'migratelp' command to move each LP from PP1(on vpath49) to PP2(on vpath36).
If your output (post mirror split) is something like the sample output:

# lslv -m P03datap4l2lv P03datap4l2lv:N/A LP    PP1  PV1               PP2  PV2               PP3  PV3 0001  0146 vpath49 0002  0147 vpath49 0003  0148 vpath49 0004  0149 vpath49 ...

Your commands would be:

migratelp P03datap4l2lv/1 vpath36/146 migratelp P03datap4l2lv/2 vpath36/147 migratelp P03datap4l2lv/3 vpath36/148 migratelp P03datap4l2lv/4 vpath36/149 ...

This would preserve the same shape/location of the data on the LUN as it had pre-split.
#AIX-Forum

Originally posted by: tony.evans

Thanks, I completed the migrations two days ago (I prefer migratepv -l lvname sourcepv targetpv just to remove any doubt).

Took around 2.5 hours per 400GB LUN.

I'm fine managing LUNs, I'm trying to understand why AIX took the decision to remove the mirror from PV's I never listed.

I checked and double checked the commands I ran (fc -l 1) and I ran the right commands. The only thing I can think is that some combination of superstrict and the placement of mirrored PP's caused AIX to remove mirrored PP's I didn't list.

I think these were the only LV's which had partitions from mirror1 on one of the disks I was removing, all the others were only mirror2 PP's. Now I don't believe that should make any difference, but I'm struggling to see what else could have generated this behaviour (and so far, no response to my PMR other than a request for a comprehensive snap).
#AIX-Forum

Originally posted by: tony.evans

I've had a response from LVM 2nd line guys. Essentially, rmlvcopy is working as intended.

The logical volume in question was mirrored with superstrict enabled. The two LUNs passed on the command line had PP's from mirror copy 1 and mirror copy 2 on them. rmlvcopy chose one of the copies to keep, and removed the other copy from all LUNs even if they weren't specified on the command line.

This only happens when superstrict is in use, the recommendation is either set the mirror to strict first, or deal with the behaviour.

I've asked if they change rmlvcopy so it at least let's you know it's not doing what you asked, or doesn't continue saying it will break superstrict mirroring policy settings.
#AIX-Forum