Technote (FAQ)echnote (FA)
Question
Increasing the size of a paging space.
Answer
Environment
OS level: AIX 4.3.3 and above
The following are the steps and an example of how to increase the size of a paging space.
1. Determine the Physical Partitions (PP) size of the volume group, enter:
# lsvg rootvg
3. Determine what hdisk the paging space is on and if there are free PP's by running:
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
hd6 hdisk0 rootvg 512MB 1 yes yes lv
So hd6 is on hdisk0.
Now determine if there are free PP's. Enter the following:
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk0 active 542 484 108..92..67..108..10
7. How much more do you want to add? For example, if adding 1.5G (1536M), you would need an additional 48
partitions.
Amount needed (1536M) divided by PP Size (32M)equals number of additional logical partitions.
1536mg/32mg = 48 partitions
8. Add the additional number of partitions.
# smit pgsp
Choose Change/Show Characteristics of a paging space.
Choose your paging space.
For example:
hd6, paging00, paging01....
At the NUMBER of additional logical partitions line, input the number derived in item 3
above (from the example, this would be 48).
Press Enter after making all desired changes.
9. Verify paging space size, enter:
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
hd6 hdisk0 rootvg 2048MB 1 yes yes lv
If during the mksysb restoration process you get the error Over mounting /., you most probably have some missing filesets on the spot that should be present for the mksysb you are using or mksysb and spot you are using are not on the same level.
Solution:
The best way is to re-create the spot from the mksysb image (mksysb_server1) you are trying to restore.
The best way is to re-create the spot from the mksysb image (mksysb_server1) you are trying to restore.
Source mksysb image:
[gzaix:root:/home/root:] lsnim -l mksysb_server1
mksysb_server1:
class = resources
type = mksysb
Rstate = ready for use
prev_state = unavailable for use
location = /export/mksysb/server1.14mar2012.sysb
version = 5
release = 3
mod = 12
oslevel_r = 5300-12
alloc_count = 0
server = master
creation_date = Thu Mar 15 02:06:46 2012
Create a spot from mksysb (mksysb_server1)
Define a Resource
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Resource Name [/export/spot/spot_server1]
* Resource Type spot
* Server of Resource [master] +
Source of Install Images [/export/mksysb/mksysb_server1] +
* Location of Resource [/export/spot/spot_server1/] /
NFS Client Security Method [] +
NFS Version Access [] +
EXPAND file systems if space needed? yes +
Comments []
installp Flags
PREVIEW only? (install operation will NOT occur) no +
COMMIT software updates? no +
SAVE replaced files? yes +
AUTOMATICALLY install requisite software? yes +
OVERWRITE same or newer versions? no +
VERIFY install and check file sizes? No
Command: running stdout: yes stderr: no
Before command completion, additional instructions may appear below.
Creating SPOT in "/export/spot/spot_server1/" on machine "master" from "mksysb_server1" ...
Restoring files from BOS image. This may take several minutes ...
Checking filesets and network boot images for SPOT "spot_server1".
This may take several minutes ...
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
Creating SPOT in "/export/spot/spot_server1/" on machine "master" from "mksysb_server1" ...
Restoring files from BOS image. This may take several minutes ...
Checking filesets and network boot images for SPOT "spot_server1".
This may take several minutes ...
warning: 0042-001 m_mkspot: processing error encountered on "master":
0042-175 c_ch_nfsexp: An unexpected result was returned by the
"/usr/sbin/exportfs" command:
exportfs: /export/mksysb/server1.14mar2012.sysb: No such file or directory
Of course, warnings may appear but don't worry.
Mirroring the rootvg Volume Group for AIX
Technote (FAQ)
Question
Mirroring the rootvg Volume Group for AIX
Answer
This document specifies the supported method for mirroring the rootvg volume group to provide high availability access of the AIX operating system. There are four steps required in mirroring rootvg:
- Mirror rootvg using mirrorvg or mklvcopy.
- Make the new mirrored disk bootable by running bosboot.
- Add the new mirrored disk to the bootlist.
- Reboot the system to disable quorum. (5300-06 and below only)
This function is not supported on /usr client, diskless client, or dataless client systems.
Mirroring the rootvg volume group is important because:
- Maintaining an active mirrored copy of the rootvg volume on another disk ensures continuous operation of the AIX operating system in the event that a disk that is part of the operating system experiences failure.
- Such maintenance provides the ability to boot more than one disk of the rootvg in the event that another boot disk has failed. In some cases, the ability to boot from alternate disks may require some user intervention.
- To mirror the entire contents of rootvg volume group, use the mirrorvg command. Assuming rootvg is on hdisk0 and thathdisk1 is the physical volume to mirror to, use the following syntax:
2. mirrorvg rootvg hdisk1
You will receive a message similar to:
AIX 5300-06 and below:
0516-1124 mirrorvg: Quorum requirement turned off, reboot system for this to take effect for rootvg.
0516-1126 mirrorvg: rootvg successfully mirrored, user should perform
bosboot of system to initialize boot records. Then, user must modify
bootlist to include: hdisk1 hdisk0.
AIX 5300-07 and above:
0516-1804 chvg: The quorum change takes effect immediately.
0516-1126 mirrorvg: rootvg successfully mirrored, user should perform
bosboot of system to initialize boot records. Then, user must modify
bootlist to include: hdisk1 hdisk0.
If user has user-created logical volumes in rootvg and does not want to mirror those, the mklvcopy command may be used instead to mirror only the standared rootvg logical volumes, such as hd1, hd2, hd3, hd4, hd5, hd6, hd8, hd9var and hd10optat AIX V5. Syntax of mklvcopy is as follows:
mklvcopy LVname 2 hdisk1
If user has other paging devices, in addition to hd6, it is recommended to mirror those as well.
If hd5 consists of more than one logical partition, then, after mirroring hd5, the user must verify that the mirrored copy of hd5resides on contiguous physical partitions. This can be verified with the following command:
lslv -m hd5
If the mirrored hd5 partitions are not contiguous, the user must delete the mirror copy of hd5 (on hdisk1) and rerun themklvcopy command for hd5, using the -m option. The user should consult documentation on the usage of the -m option for themklvcopy command.
If rootvg is mirrored using mklvcopy command, the user must manually synchronize the partitions and disable quorum.
syncvg -v rootvg =>will synchronize all stale partitions
chvg -Qn rootvg =>will disable quorum
- To initialize the boot record on the newly mirrored disk, run the following:
4. bosboot -ad /dev/hdisk1
- To add the newly mirrored disk to the bootlist, run the following:
6. bootlist -m normal hdisk0 hdisk1
NOTE: If the system is booted via network, you may need to include the ent# in the bootlist.
WARNING: Even though this command identifies the list of possible boot disks, it does not guarantee that the system will boot from the alternate disk in all cases involving failures of the first disk. In such situations, it may be necessary for the user to boot from the installation or maintenance media: select Maintenance, reissue the bootlist command leaving out the failing disk, and then reboot. On some models, firmware provides a utility for selecting the boot device at boot time. This may also be used to force the system to boot from the alternate disk.
- If necessary, reboot system to disable quorum, by running either one of the following commands:
8. reboot
or
shutdown -Fr
AIX 5.3
IY67833 POSSIBLE DATA LOSS OR CORRUPTION AFTER USING CHVG -B OR -G
IY69185 AFTER MIGRATING BIG VG FROM 5.2 TO 5.3, EXTENDVG FAILS
IY71108 EXTENDVG DOES NOT WRITE VGDA TO NEW DISKS
AIX 5.2
IY41715 MKLVCOPY: SUPERSTRICT OPTION DOES NOT WORK AS DISCRIBED IN DOC
IY41740 MKLVCOPY WITH THE SYNCHRONIZE OPTION (-K) WILL HANG
IY37746 ENHANCED CONCURRENT SYNCVG FAILURES WITH I/O
IY40990 CHANGES TO LVCB/ODM NOT PROPAGATED TO REMOTE NODES BY EXTENDLV OR MKLVCOPY
AIX 5.1
IY41556 MKLVCOPY WITH THE SYNCHRONIZE OPTION (-K) WILL HANG
IY34117 MKLVCOPY OF LV ON >32 DISKS TO >32 DISKS CAUSES ALLOCP COREDUMP
IY37229 ENHANCED CONCURRENT MKLVCOPY FAILS WITH 64 BIT KERNEL
IY37897 ENHANCED CONCURRENT SYNCVG FAILURES WITH I/O
IY38022 MKLVCOPY RUNS OUT OF ENVIRONMENT SPACE WITH LARGE LV
IY40939 CHANGES TO LVCB/ODM NOT PROPAGATED TO REMOTE NODES BY EXTENDLV OR MKLVCOPY
IY44118 MKLVCOPY FAILS WITHOUT ERROR ON STRIPED LV
IY18954 MKLVCOPY: COMMAND WITH -U AND -S S OPTION FAIL
IY19718 MIRROR LV ACTION GENERATES A NON CONFIRM MKLVCOPY COMMAND
IY40586 MKLVCOPY FAILS FOR 3 COPIES OF STRIPED LV
IY24374 SYNCVG ERROR WITH BAD BLOCK RELOCATION IN CONCURRENT MODE
IY25551 SYNCVG INTERMITTENTLY HANGS
IY25552 SYNCVG -V DOESN'T SYNC ALL PARTITIONS
IY41329 CNTRL-C DURING SYNCVG NOT CLEANING UP
IY45152 SYNCVG FAILS TO SYNC STALE PARTITIONS
IY32881 SYNCVG ON ENHANCED CONCURRENT VG HANGS WITH -P 2 OR HIGHER
IY34959 VOLUME GROUP CORRUPTION AFTER MIGRATION TO AIX 5
IY31649 PPS FAIL TO SYNC ON DISK WITH > 2¬15 PPS
IY37897 ENHANCED CONCURRENT SYNCVG FAILURES WITH I/O
IY45151 SYNCVG FAILS TO SYNC STALE PARTITIONS
IY35272 517 OR 553 LED HANG MINUTES ON SYNCVG ROOTVG IF TCB INSTALLED
No comments:
Post a Comment