Recreating LV mirror

[rusher]

Hello,

I had a fixed disk (hdisk25) fail on an AIX server version 4.3 performed the following steps to replace it. I removed it from the lv (dmdlv3) and then the vg (dmdvg2) and then removed it from the OS and physically removed the drive from the server. I then added a replacement and ran cfgmgr and the OS assigned it to hdisk 25 again. I then extended the dmdvg2 with hdisk25, but I am running into issues getting the dmdlv mirrored again. lslv -l dmdlv3 has the following output:
dmdlv3:/udb/data1
PV COPIES IN BAND DISTRIBUTION
hdisk5 541:000:000 20% 109:107:108:108:109
hdisk9 206:000:000 0% 109:097:000:000:000
hdisk24 667:000:000 32% 000:017:216:217:217

How do I readd the hdisk25 into the lv and setup the mirroring again?

Thanks,

Bill

LOGICAL VOLUME: dmdlv3 VOLUME GROUP: dmdvg2
LV IDENTIFIER: 000177068dc44d89.2 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 2032 PP SIZE: 16 megabyte(s
COPIES: 1 SCHED POLICY: parallel
LPs: 1414 PPs: 1414
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: inner edge UPPER BOUND: 32
MOUNT POINT: /udb/data1 LABEL: /udb/data1
MIRROR WRITE CONSISTENCY: on
EACH LP COPY ON A SEPARATE PV ?: yes

 

[RMGBELGIUM]

mklvcopy dmdlv3 2 hdisk25
syncvg -l dmdlv3

rgds,

R.

 

[rusher]

Thanks RMGBELGIUM! I did try what your suggested, but I get the following error:

root@dmxams:/dmd/util(385)$ mklvcopy dmdlv3 2 hdisk25
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics.

I am thinking that perhaps I need to extend the lv so that it sees/utilizes the hdisk25, but when I've looked at it in smitty it asks for the number of additional logical partitions to add. I'm unclear what the number of logical partitions would need to be.

 

[RMGBELGIUM]

I assumed the hdisk25 was big enough to contain a full copy of the LV.Could you post the output of :

lspv hdisk25
lspv hdisk9
lspv hdisk5
lspv hdisk24

So we can see how much space is available on each disk

rgds,

R.

 

[rusher]

Here is the output:










root@dmxams:/(130)$ lspv hdisk25
PHYSICAL VOLUME: hdisk25 VOLUME GROUP: dmdvg2
PV IDENTIFIER: 0001770683e13bba VG IDENTIFIER 000177068dc44d89
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 0
TOTAL PPs: 1084 (17344 megabytes) VG DESCRIPTORS: 1
FREE PPs: 1084 (17344 megabytes)
USED PPs: 0 (0 megabytes)
FREE DISTRIBUTION: 217..217..216..217..217
USED DISTRIBUTION: 00..00..00..00..00
root@dmxams:/(131)$ lspv hdisk9
PHYSICAL VOLUME: hdisk9 VOLUME GROUP: dmdvg2
PV IDENTIFIER: 000177068dc40ac3 VG IDENTIFIER 000177068dc44d89
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 2
TOTAL PPs: 542 (8672 megabytes) VG DESCRIPTORS: 1
FREE PPs: 335 (5360 megabytes)
USED PPs: 207 (3312 megabytes)
FREE DISTRIBUTION: 00..10..108..108..109
USED DISTRIBUTION: 109..98..00..00..00
root@dmxams:/(132)$ lspv hdisk5
PHYSICAL VOLUME: hdisk5 VOLUME GROUP: dmdvg2
PV IDENTIFIER: 000177068dc3e4a3 VG IDENTIFIER 000177068dc44d89
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 2
TOTAL PPs: 542 (8672 megabytes) VG DESCRIPTORS: 1
FREE PPs: 0 (0 megabytes)
USED PPs: 542 (8672 megabytes)
FREE DISTRIBUTION: 00..00..00..00..00
USED DISTRIBUTION: 109..108..108..108..109
root@dmxams:/(133)$ lspv hdisk24
PHYSICAL VOLUME: hdisk24 VOLUME GROUP: dmdvg2
PV IDENTIFIER: 000177060d4a9e28 VG IDENTIFIER 000177068dc44d89
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 1
TOTAL PPs: 1084 (17344 megabytes) VG DESCRIPTORS: 1
FREE PPs: 417 (6672 megabytes)
USED PPs: 667 (10672 megabytes)
FREE DISTRIBUTION: 217..200..00..00..00
USED DISTRIBUTION: 00..17..216..217..217

 

[RMGBELGIUM]

Your LV mirror will have to be created over hdisk25 and hdisk24,
your LV consists of 1414 LP's, hdisk25 only offers you 1084 possible LP's -> still need 330 LP's.Hdisk24 still has 417 free PP's.
so you will get

mklvcopy dmdlv3 2 hdisk25 hdisk24
syncvg -l dmdlv3

rgds,

R.

 

[rusher]

Still getting an allocation error. Perhaps I need to remove hdisk24 from dmdlv3 and then do the same command?

root@dmxams:/(141)$ mklvcopy dmdlv3 2 hdisk25 hdisk24
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics.

 

[LuchoTB]

execute "lslv dmdlv3 " and see if you have set EACH LP COPY ON A SEPARATE PV ?: yes.

if the volume have set a "yes" change it to "no" to Allocate each logical partition copy on a SEPARATE physical volume.

/usr/sbin/chlv -s's' dmdlv3

Saludos:
Lo mio no es el ingles (se nota)

 

[rusher]

Thanks LuchoTB, but I think I messed up the lv. I ended up extending the lv as I thought that would allow me to then mirror the additional space, but that was not the right step. I think the only way to set it up with it's original configuration is to backup the dmdlv3 and then delete it and recreate it and restore from tape.

Bill