Hello

I have a box with aix 5.3

if I type lsvg -l rootvg all my filesystems are sync except one

rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 32 64 2 open/syncd N/A
hd8 jfs2log 1 2 2 open/syncd N/A
hd4 jfs2 16 32 2 open/syncd /
hd2 jfs2 70 140 2 open/syncd /usr
hd9var jfs2 12 24 2 open/syncd /var
hd3 jfs2 12 24 2 open/syncd /tmp
hd1 jfs2 12 24 2 open/syncd /home
hd10opt jfs2 12 24 2 open/syncd /opt
lg_dumplv sysdump 16 16 1 open/syncd N/A
ihslv jfs2 36 72 2 open/stale /usr/IBMIHS

My rootvg is on mirror

Can I type :

syncvg -v rootvg and I resolve this.

I dont need to break the mirror ?


Thanks for your tips.

No need to break the mirror (if you break the mirror, there will be no assignment anymore which PP is a copy of which, so what shall it sync?!), just run it.
The number of stale PPs should go to zero after some time. You can also check the number of stale PPs with just "lsvg rootvg".

Thanks zaxxon for your reply

I run the command syncvg -v rootvg but nothing happens.

I get the prompt again but I check with lsvg -l rootvg and I get the same thing

ihslv jfs2 36 72 2 open/stale /usr/IBMIHS

and If I type lsvg rootvg I got

STALE PVs: 1 STALE PPs: 36


Any suggestions.

I have another question I can type syncvg -l ihslv or I can resolve in another way.


Thanks again

Hello

I try with the option syncvg -l ihslv but the same thing nothing happen

Any other suggestions


Thanks in advance

The easiest way for syncing a stale AIX LVM mirror is
# varyonvg <stalevg>
You could consider the varyonvg command as a very basic repairvg. Varyonvg will call syncvg among other things. This will run in the background so you might see a lresynclv process in the processlist. If the lv stays stale after this finished pls post the output of
# lsvg <stalevg>
# lslv <stalelv>
# lslv -l <stalelv>

(The drawback of varyonvg might be that it syncs one PP per time. Using syncvg makes sense when syncing large mirrors as you can tell it (-P) to sync more PPs per time hence being faster. When it comes to Terrabytes this does make a difference.)

Thanks for the reply too shockneck.

Before I type varyonvg ihslv. I need to ask something, there is no problem to run this command. because this box its a production server.

I send the commands that you told me before run the command.

Thanks for the comments.


lslv -l ihslv
ihslv:/usr/IBMIHS
PV COPIES IN BAND DISTRIBUTION
hdisk0 036:000:000 0% 036:000:000:000:000
hdisk1 036:000:000 0% 036:000:000:000:000

lslv ihslv
LOGICAL VOLUME: ihslv VOLUME GROUP: rootvg
LV IDENTIFIER: 0009d3bc0000d600000001095659b58d.12 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/stale
TYPE: jfs2 WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 128 megabyte(s)
COPIES: 2 SCHED POLICY: parallel
LPs: 36 PPs: 72
STALE PPs: 36 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: /usr/IBMIHS LABEL: /usr/IBMIHS
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO

lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 0009d3bc0000d600000001095659b58d
VG STATE: active PP SIZE: 128 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1092 (139776 megabytes)
MAX LVs: 256 FREE PPs: 668 (85504 megabytes)
LVs: 11 USED PPs: 424 (54272 megabytes)
OPEN LVs: 10 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 1 STALE PPs: 36
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per VG: 32512
MAX PPs per PV: 1016 MAX PVs: 32
LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable

The information about your vg/lv is looking good. There is no risk in running a varyonvg against an already active volume group. Indeed varyonvg is meant to be used like this as it repairs some vg problems.