MIRRORVG RUN FOR ERROR!! 1

[7280]

Hi,
I wanted to check if my disks were mirrored, so looking to man pages I found:
To get default mirroring of rootvg, enter:
mirrorvg rootvg
rootvg now has two copies.

I thought this command simply has to tell me if a mirror exists or not but after I ran it, it seems mirroring!

On this system I have rootvg which has assigned 2 disks:
lspv
hdisk0 00c7632f06f1e5fd rootvg active
hdisk1 00c548dc8e83def7 rootvg active

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 16 32 2 open/syncd N/A
hd8 jfs2log 1 2 2 open/syncd N/A
hd4 jfs2 1 2 2 open/syncd /
hd2 jfs2 12 24 2 open/syncd /usr
hd9var jfs2 5 10 2 open/syncd /var
hd3 jfs2 11 22 2 open/syncd /tmp
hd1 jfs2 1 2 2 open/syncd /home
hd10opt jfs2 121 242 2 open/syncd /opt
lg_dumplv sysdump 8 8 1 open/syncd N/A
wasapplv jfs2 16 16 1 open/syncd /usr/WebSphere/AppServer
wasloglv jfs2 2 2 1 open/syncd /usr/WebSphere/AppServer/logs


lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 00c548dc00004c000000010a8e83fa56
VG STATE: active PP SIZE: 128 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1092 (139776 megabytes)
MAX LVs: 256 FREE PPs: 728 (93184 megabytes)
LVs: 12 USED PPs: 364 (46592 megabytes)
OPEN LVs: 11 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: no
MAX PPs per VG: 32512 0
MAX PPs per PV: 1016 MAX PVs: 32
LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable


Though now it seems mirroring. But I don't understand one thing.
rootvg has 2 disks assigned so since the system wasn't mirrored, the data had to be written to both disks, right?
If this is true now where the system is doing the mirror?

Last thing please. Now I'm letting the command terminate, but what happens tonight when mksysb backup starts. Does a problem occur? Will my backup be consistent?

Thanks in advance. Please advice, very urgent! It's a PROD system.

 

[samirm]

When you see 1 LP = 2 PP ( double in size)and LV State is Open/syncd
Means you are done with your mirroring. Your data is safe.

But, at this time for following LP not eqaul to double :-

wasapplv jfs2 16 16 1 open/syncd /usr/WebSphere/AppServer
wasloglv jfs2 2 2 1 open/syncd /usr/WebSphere/AppServer/logs

So these two LVs are not mirrored.

The mirroring is happening among hdisk0 and hdisk1. If you see LV State is showing open/stale, means your data is not synced among the disks.

mksysb is just taking your rootvg backup.
So this is not related with your mirroring. There will be no issue.

Sam

 

[7280]

Hi,
it's about 16 hours that the mirrorvg is running. I have only one disk of 70gb. Is it possible it takes so much?
Is there a log or something else that shows percentage of mirroring?
If I run lsvg -l rootvg command just stays running but no output is given so I have to stop help.
Is everything ok?
I don't see error messages in errpt.

Thanks.

 

[7280]

Error of lsvg -l rootvg is:
0516-1201 lsvg: Warning: Volume group rootvg is locked. This command
will continue retries until lock is free. If lock is inadvertent
and needs to be removed, execute 'chvg -u rootvg'.
^C

 

[7280]

in this moment, after 16 hours execution, the command failed with this error:

0516-1201 lsvg: Warning: Volume group rootvg is locked. This command
will continue retries until lock is free. If lock is inadvertent
and needs to be removed, execute 'chvg -u rootvg'.

but prompt is not returned.
what should I do?
run chvg -u rootvg from another shell?
do I need also to manually kill the mirrorvg command?
thanks.

 

[7280]

After I ran chvg -u rootvg I received this message on the mirrorvg shell:
grep: 0652-033 Cannot open /tmp/non_single671988.
0516-921 rmlvcopy: All logical partitions have less than or
equal to 1 number of copies.
grep: 0652-033 Cannot open /tmp/non_single671988.
0516-921 rmlvcopy: All logical partitions have less than or
equal to 1 number of copies.
grep: 0652-033 Cannot open /tmp/non_single671988.
0516-921 rmlvcopy: All logical partitions have less than or
equal to 1 number of copies.

Now mirrorvg is not running anymore. But how can I know if the mirror is consistent or not?

Thanks

 

[MirkoC]

what are the outputs of the commands "lsvg -l rootvg" and "lsvg -p rootvg"?

 

[7280]

root@bw-docsrv2: / # 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 16 32 2 open/syncd N/A
hd8 jfs2log 1 2 2 open/syncd N/A
hd4 jfs2 1 2 2 open/syncd /
hd2 jfs2 12 24 2 open/syncd /usr
hd9var jfs2 5 10 2 open/syncd /var
hd3 jfs2 11 22 2 open/syncd /tmp
hd1 jfs2 1 2 2 open/syncd /home
hd10opt jfs2 121 242 2 open/syncd /opt
lg_dumplv sysdump 8 8 1 open/syncd N/A
wasapplv jfs2 9 9 1 open/syncd /usr/WebSphere/AppServer
wasloglv jfs2 1 1 1 open/syncd /usr/WebSphere/AppServer/logs
sysmgmtlv jfs2 9 9 1 open/syncd /sysmgmt
root@bw-docsrv2: / # lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk1 active 546 360 109..33..00..109..109
hdisk0 active 546 367 109..40..00..109..109

Thanks.

 

[MirkoC]

I think that it's better if you unmirror the volume group with the command "unmirrorvg rootvg". After that repeat the command "lsvg -p rootvg".

Mirko

 

[MirkoC]

In order to clean up the situation, you can force the fact that all the data are on a single disk, for example on the hdisk0, through the command “migratepv hdisk1 hdisk0”. Therefore you will be able launch the activity of mirror newly, through the command “mirrorvg -S -m rootvg hdisk1”.
Remember that for the mirror of rootvg, you must also modify the bootlist (“bootlist –m normal –o hdisk0 hdisk1”) and launching the command “bosboot” on each disk (“bosboot –a –d hdisk0;bosboot –a –d hdisk1”).

You can always verify the outcome of the job launch the command “lsvg –l rootvg”.

Ciao!

 

[7280]

Thanks MirkoC.
But why you think I need to rerun mirror?
What output didn't convince you?

Thanks again

 

[MirkoC]

In a correct configuration every copy of the filesystem is present on all disk. Therefore for every fileystem you must have two copies. Launch the commando “lsvg –l rootvg”, instead we can be seen that for three filesystem an only copy exists. You could correct only this error, but I believe it’s better to begin again with the procedure from the unmirror of rootvg (“unmirrorvg rootvg”), the movement of the data on a single disk (“migratepv hdisk1 hdisk0”), the mirror of the data (“mirrorvg -S -m rootvg hdisk1”), the modification of bootlist (“bootlist –m normal –o hdisk0 hdisk1”) and at last the bosboot (“bosboot –a –d hdisk0;bosboot –a –d hdisk1”).

Ciao!