migrating a pv to another - concurrent vg
- From: Holger.VanKoll@xxxxxxxxxxxx
- Date: Wed, 25 Jan 2006 17:03:28 +0100
Title: migrating a pv to another - concurrent vg
Hello,
I need to migrate hdisk19 to hdisk10. However, they contain the same LV. So, lv xx is "striped" between hdisk19 and hdisk10.
So, migratepv of course does not work.
(0)root@sbe18950 605# migratepv dlmfdrv19 dlmfdrv10
0516-1244 migratepv: Destination physical volume dlmfdrv10 contains
partitions of the logical volume poms1Data1a.
0516-812 migratepv: Warning, migratepv did not completely succeed;
all physical partitions have not been moved off the PV.
In these cases I always used lmigratepp. It can be a lot of work as you have to move every single pp, but it always worked.
So I tried it (the variables v/pvi19/pvi10 are set correctly!) and it gave
(0)root@sbe18950 603# lmigratepp -g $v -p $pvi19 -n 257 -P $pvi10 -N 636
0516-090 lmigratepp: This node unable to get configuration lock for this
concurrent volume group.
Its the first time that I have problems with lmigratepp. This is a enhanced concurrent VG. I am not sure if I already used lmigratepp on a e.c. VG.
To me it looks that you cannot use lmigratepp on a e.c. VG.
Are there other ways? I thought about reorgvg, but that gives few control.
If there is no other way, I will add disks, mirror the LV (thats on hdisk10+19) to them, drop the old primary copy and re-mirror on hdisk10.
Regs,
Holger
- Prev by Date: Re: another rootvg question
- Next by Date: errpt not clear to me
- Previous by thread: another rootvg question
- Next by thread: Re: migrating a pv to another - concurrent vg
- Index(es):