ITEM: F6149L

migratepv problem

Question:

We are at AIX 3.2.4 . We tried to migrate data from one disk to another
of the same size. We did migratepv hdx hdy. Then we thought the system
hung or something happened and thought that migratepv wasn't working
since it took quite a while and nothing seemed to be happening. We typed
lspv and got message that vg is locked. So we removed the lock with
"putlvodm -K `getlvodm -v lv31`". Then we did lspv and got message that
"map file already in use".  migratepv then exited with the "map file
already in use" message. So we restarted migratepv and it completed.
But now lspv -M shows lv31: 144:1 and lv31:144:2.  Looks like we have
mirroring for that one pp for some reason.

"lslv lv31" gives the following errors: 

  0516-022 illegal parameter or structure value
  0516-304 lslv: unable to find device id in device config database

and there are ? marks for stale pps.

How can I fix this strange situation?

Response:

Interrupting migratepv will sometimes result in partitions that seemed
to be mirrored even though the logical volume itself is not mirrored.

We issued the command:  "lslv lv31" which returned that Copies = 1, so
this logical volume is not being mirrored.

We decided to run syncvg to make sure everything was sync'ed properly:

  syncvg -f -l lv31

This completed successfully.

We then ran the following commands to get the logical partition map for
logical partition 144:

   lquerylv -L`getlvodm -l lv31` -r > /tmp/map.lv31
   grep 144 /tmp/map.lv31 > /tmp/map.lv31.144

We then editted /tmp/map.lv31.144.  We decided to remove the copy on 
physical partition 166, so we deleted all other lines and left only the 
line that described physical partition 166 in the file.

We then ran the following command to remove physical partition 166
from the logical volume:

   lreducelv -l`getlvodm -l lv31` -s 1 /tmp/map.lv31.144

At this point lslv, lspv, lspv -M, and fsck all ran clean.



Support Line: migratepv problem ITEM: F6149L

Dated: February 1994 Category: N/A

This HTML file was generated 99/06/24~13:30:51

Comments or suggestions?
Contact us