Login or Register to Ask a Question and Join Our Community


AIX

syncvg

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems AIX syncvg
# 8  
Old 07-10-2008
syncvg
I type the command varyonvg ihslv to try to repair the stale error

and It doesnt work

varyonvg ihslv
0516-008 varyonvg: LVM system call returned an unknown
error code (3).

I got the same thing on these commands like yesterday when I typed

Code:
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

Code:
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

My fs still look like this

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

Thanks for your tips
# 9  
Old 07-10-2008
Quote:
Originally Posted by lo-lp-kl
I type the command varyonvg ihslv to try to repair the stale error

and It doesnt work

varyonvg ihslv
0516-008 varyonvg: LVM system call returned an unknown
error code (3).

[...]
It worked in a sense that now I can tell you that your ODM is corrupted. To repair an inconsistency between the device configuration database and the LVM information you could try the synclvodm command:
# synclvodm -v -P rootvg ihslv
# 10  
Old 07-10-2008
syncvg
Thanks again shockneck

I type the command

Code:
synclvodm -v -P rootvg ihslv
synclvodm: Physical volume data updated.
synclvodm: Logical volume ihslv updated.

lsvg -l rootvg
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

Now I have to type the command syncvg -v rootvg or syncvg -l ihslv or varyonvg ihslv which one itīs best.

Thanks, many thanks
# 11  
Old 07-10-2008
Do you have a bad disk? Are there any P/H errors logged on the disk? If there are, run diags on it. If that runs clean, break the mirror, remove it from rootvg and run diags again, format it and then re-add it to the VG.
# 12  
Old 07-11-2008
Quote:
Originally Posted by lo-lp-kl
[...]
I type the command

synclvodm -v -P rootvg ihslv
synclvodm: Physical volume data updated.
synclvodm: Logical volume ihslv updated.

[...]
Use varyonvg again, to see whether the error has gone. If it did, check that lresynclv is running. Wait for completion and check again.
# 13  
Old 07-11-2008
syncv
Thanks again shockneck

I try again the varyonvg again but I got the same error

varyonvg ihslv
0516-008 varyonvg: LVM system call returned an unknown
error code (3).

Its better if I pick up a pmr to Ibm or I can do something else to resolve this.
# 14  
Old 07-11-2008
Quote:
Originally Posted by lo-lp-kl
[...]
I try again the varyonvg again but I got the same error

varyonvg ihslv
0516-008 varyonvg: LVM system call returned an unknown
error code (3).[...]
That's odd. Using fsck or recreating the LV would both be disruptive to service. Given that you use IHS with that stale mirror an online repair should still be possible. Hence next thing I would try is

- if you have two disks in your server that can be used by rootvg:
breaking the LV mirror and mirroring the LV anew. If you did not already - backup your FS data (e.g. tar locally to another filesystem) before you start.
# rmlvcopy ihslv 1
Important: do not give any information about from which disk the mirror copy should be removed but let LVM sort this out. LVM should detect and keep the good copy. Immediately after removing the copy you can mirror the LV again:
# mklvcopy ihslv 2
# varyonvg rootvg
wait till sync'd, check.

- if you have three disks (could be connected temporarily) in your server that can be used by rootvg:
Extend rootvg to this disk and make a third mirror copy on the third disk
# extendvg rootvg hdisk2
# mklvcopy ihslv 3 hdisk2
# varyonvg rootvg
wait till sync'd! Only then do
# rmlvcopy ihslv 2 hdisk1
# rmlvcopy ihslv 1 hdisk0
Then rebuild copies on the original disks:
# mklvcopy ihslv 2 hdisk0
# mklvcopy ihslv 3 hdisk1
# varyonvg rootvg
wait till sync'd, check, if OK remove third mirror copy
# rmlvcopy ihslv 2 hdisk2
Reduce rootvg.
# reducevg rootvg hdisk2
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. AIX

Syncvg

Hello, I currently migrate a VG from one storage to another one with mirrorvg. Does anyone know, if a syncvg copy the whole stale pps, regardless if the overlying fs is nearly empty? Or will only the used space copied? Regards (2 Replies)
Discussion started by: -=XrAy=-
2 Replies
Login or Register to Ask a Question