Preparing file systems on AIX systems
You must create volume groups, logical volumes, and file systems for the server by using the AIX® Logical Volume Manager.
Procedure
-
Increase the queue depth and maximum transfer size for all of the available
hdiskX disks. Issue the following commands for each disk:
Do not run these commands for operating system internal disks, for example, hdisk0.chdev -l hdisk4 -a max_transfer=0x100000 chdev -l hdisk4 -a queue_depth=32 chdev -l hdisk4 -a reserve_policy=no_reserve chdev -l hdisk4 -a algorithm=round_robin -
Create volume groups for the IBM
Storage Protect
database, active log, archive log, database backup, and storage pool. Issue the
mkvg command, specifying the device IDs for corresponding disks that you
previously identified.
For example, if the device names hdisk4, hdisk5, and hdisk6 correspond to database disks, include them in the database volume group and so on.System size: The following commands are based on the medium system configuration. For small and large systems, you must adjust the syntax as required.
mkvg -S -y tsmdb hdisk2 hdisk3 hdisk4 mkvg -S -y tsmactlog hdisk5 mkvg -S -y tsmarchlog hdisk6 mkvg -S -y tsmdbback hdisk7 hdisk8 hdisk9 hdisk10 mkvg -S -y tsmstgpool hdisk11 hdisk12 hdisk13 hdisk14 ... hdisk49 -
Determine the physical volume names and the number of free physical partitions to use when
you create logical volumes. Issue the lsvg for each volume group that you
created in the previous step.
For example:
The output is similar to the following. The FREE PPs column represents the free physical partitions:lsvg -p tsmdbtsmdb: PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION hdisk4 active 1631 1631 327..326..326..326..326 hdisk5 active 1631 1631 327..326..326..326..326 hdisk6 active 1631 1631 327..326..326..326..326 -
Create logical volumes in each volume group by using the mklv command.
The volume size, volume group, and device names vary, depending on the size of your system and
variations in your disk configuration.
For example, to create the volumes for the IBM Storage Protect database on a medium system, issue the following commands:
mklv -y tsmdb00 -t jfs2 -u 1 -x 1631 tsmdb 1631 hdisk2 mklv -y tsmdb01 -t jfs2 -u 1 -x 1631 tsmdb 1631 hdisk3 mklv -y tsmdb02 -t jfs2 -u 1 -x 1631 tsmdb 1631 hdisk4 -
Format file systems in each logical volume by using the crfs
command.
For example, to format file systems for the database on a medium system, issue the following commands:
crfs -v jfs2 -d tsmdb00 -p rw -a logname=INLINE -a options=rbrw -a agblksize=4096 -m /tsminst1/TSMdbspace00 -A yes crfs -v jfs2 -d tsmdb01 -p rw -a logname=INLINE -a options=rbrw -a agblksize=4096 -m /tsminst1/TSMdbspace01 -A yes crfs -v jfs2 -d tsmdb02 -p rw -a logname=INLINE -a options=rbrw -a agblksize=4096 -m /tsminst1/TSMdbspace02 -A yes -
Mount all of the newly created file systems by issuing the following command:
mount -a -
List all file systems by issuing the df command.
Verify that file systems are mounted at the correct LUN and correct mount point. Also, verify the available space.The following example of command output shows that the amount of used space is typically 1%:
tapsrv07> df -g /tsminst1/* Filesystem GB blocks Free %Used Iused %Iused Mounted on /dev/tsmact00 195.12 194.59 1% 4 1% /tsminst1/TSMalog - Verify that the user ID you created in Creating the user ID and directories for the server instance has read and write access to the directories for the server.