increase size of file system

[rickjet]

I need to increase the size of
/dev/hd2 786432 7520 100% 23464 12% /usr

I use the command

chfs -a size=888832 /usr

to increase it by 100mb but everytime I do it I get this

lquerypv: Warning, physical volume hdisk0 is excluded since it may be
either missing or removed.
lquerypv: Warning, physical volume hdisk1 is excluded since it may be
either missing or removed.
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics

can someone please help me? I am very new to AIx

 

[unixfreak]

Please cut&paste the output of 'lspv' and 'lquerypv -At hdisk0'

Thanks
Henrik Morsing

 

[rickjet]

lspv

hdisk2 000bf9bfc505253b rootvg active
hdisk3 000bf9bfc5056463 rootvg active
hdisk4 none None
hdisk5 000bf9bf50c6e03d datavg active

I'm not sure if I'm doiong the 'lquerypv -At hdisk0'

0516-108 lquerypv: PV identifier not entered.
Usage: lquerypv [ -h /dev/PVname | [ -p PVid [-g VGid | -N PVname] [-scPnaDdAt]
]

 

[raztaboule]

can you post :
lslv -l hd2
and
lsdev -Cc disk

thanks.

 

[rickjet]

# lslv -l hd2
hd2:/usr
PV COPIES IN BAND DISTRIBUTION
hdisk0 012:000:000 100% 000:000:012:000:000
hdisk1 012:000:000 100% 000:000:012:000:000
hdisk2 012:000:000 100% 000:000:012:000:000
#

# lsdev -Cc disk
hdisk0 Defined 1S-08-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk1 Defined 1S-08-00-9,0 16 Bit LVD SCSI Disk Drive
hdisk2 Available 25-08-00-9,0 16 Bit LVD SCSI Disk Drive
hdisk3 Available 25-08-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk4 Available 1s-08-01 MPIO Other FC SCSI Disk Drive
hdisk5 Available 1s-08-01 MPIO Other FC SCSI Disk Drive

 

[makesysb]

Hello there,

Please run these commands, cut and paste the outputs: to this screen:

lsvg -o

lsvg -l rootvg

lscfg -v | grep disk

lslv -m hd5

thanx
SA

 

[makesysb]

Hello there ,


Also once you cut & paste the above mentioned output,

do this from the command prompt and let know the output:

df -k

df -kv /usr

and then after that run chfs -a size=+-------- /usr

thanx
SA

 

[uptodate]

It appears that the ODM sees rootvg on hdisk0 and hdisk1 while the output shows rootvg to be on hdisk2/hdisk3. That is why the errors:
lquerypv: Warning, physical volume hdisk0 is excluded since it may be
either missing or removed.
lquerypv: Warning, physical volume hdisk1 is excluded since it may be
either missing or removed.

Do a `bootlist -m normal -o` and see if it shows hdisk0/1 or hdisk2/3. If it is the former, then run: `lsvg -l rootvg` and see if the vg is mirrored. If so, then you could run `bosboot -ad /dev/hdisk2` and then bootlist -m normal hdisk2 hdisk3.

You can also run a `syncvg -v rootvg` just to make sure all is kosher.

Your hdisk0/1 show as defined and your chfs shows that /usr is expecting those disks, yet the output shows rootvg to be on hdisk2/3.

If you run the bootlist and bosboot successfully and your rootvg is on hdisk2/3 then your ODM got messed up somehow.

 

[raztaboule]

any hardware problem in errpt ?
if lslv hd2 says that some PV are stale and errpt says there is an hardware probleme you should reduce the number of copie for rootvg ( keeping the ones on hdisk2 of course ), remove hdisk0 and hdisk1 , call your hardware support ...

 

[rickjet]

thanks uptodate. that worked. IOU one

 

[rickjet]

One more question. what is the "ODM"?

 

[makesysb]

Hello ,

Please visit this site for more information on Object Data Management On AIX Operating System:

http://web.utanet.at/mario/exam/5129ch5.htm

thanx
sa

 

[uptodate]

The ODM is the Object Data Manager which AIX uses instead of flat files that you find in other Unix varients, such as Solaris, BSD, Linux, etc.

This describes the files in the ODM:
PdDv Predefined Devices
Contains entries for all device types currently on the system. It can also contain additional device types if the user has specifically installed certain packages that contain device support for devices that are not on the system. The term devices is used generally to mean both intermediate devices (e.g., adapters) and terminal devices (e.g., disks, printers, display terminals, and keyboards). Pseudo-devices (e.g., pseudo terminals, logical volumes, and TCP/IP) are also included there. Pseudo-devices can either be intermediate or terminal devices.

PdCn Predefined Connection
Contains connection information for intermediate devices; also includes predefined dependency information. For each connection location, there are one or more objects describing the subclasses of devices that can be connected. This information is useful, for example, in verifying whether a device instance to be defined and configured can be connected to a given device.

PdAt Predefined Attribute
Contains an entry for each existing attribute for each device represented in the Predefined Devices (PdDv) object class. An attribute, in this sense, is any device-dependent information not represented in the PdDv object class. This includes information such as interrupt levels, bus I/O address ranges, baud rates, parity settings, block sizes, and microcode file names.

Config_Rules Configuration Rules
Contains the configuration rules used by the Configuration Manager. The Configuration Manager runs in two phases during system boot. The first phase is responsible for configuring the base devices so that the real root device can be configured and made ready for operation. The second phase configures the rest of the devices in the system after the root file system is up and running. The Configuration Manager can also be invoked at run time. The Configuration Manager routine is driven by the rules in the Config_Rules object class.

CuDv Customized Devices
Contains entries for all device instances defined in the system. As the name implies, a defined device object is an object that a Define method has created in the CuDv object class. A defined device instance may or may not have a corresponding actual device attached to the system.

A CuDv object contains attributes and connections specific to the device instance. Each device instance, distinguished by a unique logical name, is represented by an object in the CuDv object class. The Customized database is updated twice, during system boot and at run time, to define new devices, remove undefined devices, or update the information for a device whose attributes have been changed.

CuDep Customized Dependency
Describes device instances that depend on other device instances. Dependency does not imply a physical connection. This object class describes the dependence links between logical devices and physical devices as well as dependence links between logical devices, exclusively. Physical dependencies of one device on another device are recorded in the Customized Device (CuDev) object class.

CuAt Customized Attribute
Device instances represented in the Customized Devices (CuDv) object class have attributes found in either the Predefined Attribute (PdAt) object class or the CuAt object class. There is an entry in the CuAt object class for attributes that take nondefault values. Attributes taking the default value are found in the PdAt object class. Each entry describes the current value of the attribute.




CuDvDr Customized Device Driver
Stores information about critical resources that need concurrence management through the use of the Device Configuration Library subroutines. You should only access this object class through these five Device Configuration Library subroutines: the genmajor, genminor, relmajor, reldevno, and getminor subroutines.

These subroutines exclusively lock this class so that accesses to it are serialized. The genmajor and genminor routines return the major and minor number, respectively, to the calling method. Similarly, the reldevno and relmajor routines release the major or minor number, respectively, from this object class.

CuVPD Customized Vital Product Data
Contains the Vital Product Data (VPD) for customized devices. VPD can be either machine-readable VPD or manually entered user VPD information.

 

[raztaboule]

that's great explanation !