Adding Storage to a System File. Post: 302495453

Sponsored Content

Operating Systems AIX Adding Storage to a System File. Post 302495453 by aix-guy on Thursday 10th of February 2011 10:13:00 AM

02-10-2011

Registered User

Ok with the AIX5.3ML11 (> ML8 is were you need to be)
you have 36096 megabytes (36GB) free in the vg to allocate without requiring the need to more disk.
you said you needed approximate 36GB to add so you are going to add it and it will go to these disk drives.

hdisk64 active 199 70 00..00..00..30..40
hdisk65 active 199 71 00..00..00..31..40
hdisk66 active 199 70 00..00..00..30..40
hdisk67 active 199 71 00..00..00..31..40

Since this is SAN disk I will assume that all the raid is handled by the back end. and you are not doing mirroring

with all that said we are going to let AIX find and place the required PP's as needed. But I do have 1 more question.
Why are the disk drives we are going to use only 199 PP's but all the others are 399 PP's.
The SAN should have allocated the same disk size to you for usage.
SO is this correct disk for the system?

Anyway you can do this in smit or

Code:

chfs -a size=+9G /sapdata5qa  (I am also assuming that this is the File System Mount and not the LV)

I would probably just round the 7.75 and the 7.50 GB's to 8.
But if you want the exact you will do the GB size the another for Meg size.

And like all things be sure you have a valid backup before you do this.

aix-guy

View Public Profile for aix-guy

Find all posts by aix-guy

LEARN ABOUT MOJAVE

device_maps

device_maps(4)                                                     File Formats                                                     device_maps(4)

NAME

       device_maps - device_maps file

SYNOPSIS

       /etc/security/device_maps

DESCRIPTION

       The  device_maps file contains access control information about each physical device. Each device is represented by a one line entry of the
       form:

       device-name : device-type : device-list :

       where

       device-name             This is an arbitrary ASCII string naming the physical device. This field contains no embedded white space  or  non-
                               printable characters.

       device-type             This is an arbitrary ASCII string naming the generic device type. This field identifies and groups together devices
                               of like type. This field contains no embedded white space or non-printable characters.

       device-list             This is a list of the device special files associated with the physical device. This field  contains  valid  device
                               special file path names separated by white space.

       The device_maps file is an ASCII file that resides in the /etc/security directory.

       Lines in device_maps can end with a `' to continue an entry on the next line.

       Comments may also be included. A `#' makes a comment of all further text until the next NEWLINE not immediately preceded by a `'.

       Leading and trailing blanks are allowed in any of the fields.

       The device_maps file must be created by the system administrator before device allocation is enabled.

       This file is owned by root, with a group of sys, and a mode of 0644.

EXAMPLES

       Example 1: A sample device_maps file

       # scsi tape
       st1:
       rmt:
       /dev/rst21 /dev/nrst21 /dev/rst5 /dev/nrst5 /dev/rst13 
       /dev/nrst13 /dev/rst29 /dev/nrst29 /dev/rmt/1l /dev/rmt/1m 
       /dev/rmt/1 /dev/rmt/1h /dev/rmt/1u /dev/rmt/1ln /dev/rmt/1mn 
       /dev/rmt/1n /dev/rmt/1hn /dev/rmt/1un /dev/rmt/1b /dev/rmt/1bn:

FILES

       /etc/security/device_maps

SEE ALSO

       allocate(1), bsmconv(1M), deallocate(1), dminfo(1M), list_devices(1)

NOTES

       The  functionality  described  in  this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for
       more information.

SunOS 5.10                                                          16 Jan 2001                                                     device_maps(4)