AIX

Hello

I have a question

I have a box with Aix 5.3 with rootvg on mirror.

I deleted a filesystem and I create a new one to install some software but when I type lsvg -l rootvg all my filesystems has mirror unless the new one.

My question is I can mirror this fs only ??? or I have to unbreak the mirror and then mirror again all the volume group (rootvg). and I can do online ?? I dont need to restart my partition



Thanks for your comments

you created a lv but forgot to tell it that it shoud consist of two mirror copies. If the unmirrored lv is located on one disk only you could mirror the lv in a two disk VG easily with

Code:

# mklvcopy <umirrored_lv> 2 <other_disk>

run varyonvg afterwards to sync.

thanks shockneck for your reply

Im sorry I dont the idea that you told me. I send a screen about my lsvg -l rootvg

$ 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 4 8 2 open/syncd N/A
hd8 jfs2log 1 2 2 open/syncd N/A
hd4 jfs2 16 32 2 open/syncd /
hd2 jfs2 55 110 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
sdump_lv sysdump 16 16 1 open/syncd N/A
Processlv jfs2 80 80 1 open/syncd /opt/IBM

the last one I need to get on mirror.

This is my lsvg rootvg output if you need it

$ lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 0009d1540000d6000000010955099d8c
VG STATE: active PP SIZE: 128 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1092 (139776 megabytes)
MAX LVs: 256 FREE PPs: 730 (93440 megabytes)
LVs: 12 USED PPs: 362 (46336 megabytes)
OPEN LVs: 11 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
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


Thanks again

right, your lv 80 PP big, is located on one disk. Use

Code:

 # lslv -l Processlv

to find out on which disk the LV is. Let us assume that it is placed on hdisk0 in your two disk rootvg. So it needs to be mirrored to the other, the second disk in rootvg assumedly hdisk1.

Code:

 # mklvcopy Processlv 2 hdisk1

This should do.

Thanks again shockneck

It works perfect

$ 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 4 8 2 open/syncd N/A
hd8 jfs2log 1 2 2 open/syncd N/A
hd4 jfs2 16 32 2 open/syncd /
hd2 jfs2 55 110 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
sdump_lv sysdump 16 16 1 open/syncd N/A
Processlv jfs2 80 160 2 open/syncd /opt/IBM


Im only have a question. when I type lslv for example hd4. I got

$ lslv -l hd4
hd4:/
PV COPIES IN BAND DISTRIBUTION
hdisk0 016:000:000 100% 000:000:016:000:000
hdisk1 016:000:000 100% 000:000:016:000:000

and in the processlv I got

$ lslv -l Processlv
Processlv:/opt/IBM
PV COPIES IN BAND DISTRIBUTION
hdisk0 080:000:000 5% 076:004:000:000:000
hdisk1 080:000:000 55% 036:044:000:000:000

There is no problem for the differences, because I think in the processlv have to be 100%


Thanks for your comments in advance

Are you concerned because of the "low" percentage value? Well, that is just an indicator how good your LV matches its position on the disk according to its definition. E.g. AIX uses ranges on disks: edge-middle-center-inner_middle-inner_edge with a preference to use center and middle areas first (to reduce movement of read-write heads). If you define that an LV has to be placed in center and all PP fit in there you get the 100%. If some or all PP in center area are taken already your LV goes somewhere else and the percent value is getting smaller.
With SAN storage this is of no interest. It may be of interest on SCSI disks e.g. in most cases for reasons of performance. One can change the LV's properties with chlv and run a reorgvg to make it look "nicer" but as long as the LV's location on the local disks does not impact performance in a bad way I'd just leave it alone.

Thank you very much Shockneck