Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

root file system 1

Status
Not open for further replies.

harpal

Technical User
Oct 3, 2001
115
0
0
GB
The root file system has hit 95% and I have tried to throw some disk space at it with smit jfs but i am getting the following error messg.

root@hqax00 / >df -v
Filesystem 512-blocks Used Free %Used Iused Ifree %Iused Mounted on
/dev/hd4 2392064 2251760 140304 95% 9820 588196 2% /

Command: failed stdout: yes stderr: no

Before command completion, additional instructions may appear below.

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.

does anyone know if there is anything I can remove that will give the root file systems more space rather then having to throw more disk space which I can't do according to the error messg.

thanks in advance


 
bro,
is your rootvg have a mirroring policy?? how big is your physical disk for your rootvg? and how many more free spaces do yo have? also , how much space do you intend to add?
 
Hi,
I think first what you need to do is:
#lsvg -p rootvg
You will see with that command how many free phisical partitions are available. If you have any ones, count them, multiple them with your PPSize for rootvg. Then you find out how much you can increase / filesystem or how big new filesystem you can create within rootvg (it's usually better then increasing /).

Bogdan
 
Well if you have no free space..you could try the following:

If root (/) is full
Check the /etc/security/failedlogin file.
Use the following command to read the contents of the file.
who /etc/security/failedlogin

The condition of tty's respawning too rapidly will create failed login entries.
To clear the file after reading or saving the output, execute the following command:

cp /dev/null /etc/security/failedlogin

Check the /dev directory.

If a device name is typed incorrectly, as in rmto instead of rmt0, a file will be
created in /dev called rmto. The command will normally proceed until the entire
root file system is filled before failing. /dev is part of the / file system. Look for
entries that are not devices (that do not have a major or minor number).

Execute the following:

cd /dev
ls -l |pg

Whereas a file size on an ordinary file would normally be seen, a device
file will have two numbers separated by a comma.

Example:
crw-rw-rw- 1 root system 12,0 Oct 25 10:19 rmt0

If the output looks like the following, the file should be removed.
crw-rw-rw- 1 root system 9375473 Oct 25 10:19 rmto

NOTE: The /dev directory has some valid file names. Look for a file that has a
large size (larger than 500 bytes).

NOTE: If system auditing is running, the /audit directory (default) may
rapidly fill up and require attention.

Check for very large files.

Large files can be located with the find command. For example, to find all
files in the root (/) directory larger than 1 MB, enter the following command:

find / -xdev -size +2048 -ls |sort -r +6

This will find all files greater than 1 MB and sort them in reverse order with
the largest files first.

NOTE: When checking the root directory, entries from the /dev directory that have
major and minor numbers instead of file sizes will be interspersed with real files
and can be ignored.

Other useful find command flags may be helpful, such as the -newer flag.
Review the product documentation to learn more about such flags.

NOTE: Before removing any files, the user should check to see if the file is currently in use by an active user process. Execute the following command:

fuser <filename>

<filename> is the file name that is being checked by the active user process. If a
file is open at the time of removal,it is only removed from the directory listing.
The blocks allocated to that file are not freed until the process holding
the file open is killed.


You can also remove smit.log and smit.script in the / directory
 
Hi,

first of all you might delete smit.script and smit.log ...
This might give you the needed free space ...

Regards
Thomas
 
also try to delete the 'core' files... Thief................
(I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us .)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top