The root file system on the ADSM server keeps filling to 100%. I have increased the file system, but after a few hours the file system is back at 100%. I have searched through the file system and have ran multiple commands to find the growing files. I am having to luck in solving this problem. Is there something else that could cause Root to fill besides growing files ?
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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
AIX Root file system keeps filling to 100% when enlarged
- Thread starter wpdavids
- Start date
wpdavids,
I would say that if you have looked thoroughly through the / filesystem and can find nothing that is causing this problem, it could be the following:
You had a file constantly being updated i.e. syslog in the root partition. Someone deleted the file without first stopping/killing the process - this means that although the file has been removed the i-nodes are still being updated and thus filling up the filesystem - an fsck will fix this but you cannot unmount / ,obviously - so I would recommend a reboot.
To see if this is the problem do the following:
You can do an fsck of the root partition now - if this is the problem you may get bad i-node map errors:
i.e.
fsck /
If you do not get these errors then this may not be the problem - but if you do you can only do a reboot to sort:
Cheers
PSD
HAMCP Specialist
I would say that if you have looked thoroughly through the / filesystem and can find nothing that is causing this problem, it could be the following:
You had a file constantly being updated i.e. syslog in the root partition. Someone deleted the file without first stopping/killing the process - this means that although the file has been removed the i-nodes are still being updated and thus filling up the filesystem - an fsck will fix this but you cannot unmount / ,obviously - so I would recommend a reboot.
To see if this is the problem do the following:
You can do an fsck of the root partition now - if this is the problem you may get bad i-node map errors:
i.e.
fsck /
If you do not get these errors then this may not be the problem - but if you do you can only do a reboot to sort:
Cheers
PSD
HAMCP Specialist
Hi
Try the "fuser -duV /filesystem" command.
This will show open files which have been unlinked from the filesystem and the user it belongs to. Using this you can look for processes belonging to that user that could be writing to that file and deal with it.
Try the "fuser -duV /filesystem" command.
This will show open files which have been unlinked from the filesystem and the user it belongs to. Using this you can look for processes belonging to that user that could be writing to that file and deal with it.
This may not be it -- but --- if there are a lot of logins with ADSM then take a look at the size of /var/wtmp file. It grows with each login, successful or not, and can fill up the /var filesystem (I know this is not the / file system) but hey, why not.
Also try looking at the root directory with "ls -la *" and see what hidden files are rather large. Sometimes .sh_history can get unwieldy.
Just my $.02 worth.
Also try looking at the root directory with "ls -la *" and see what hidden files are rather large. Sometimes .sh_history can get unwieldy.
Just my $.02 worth.
- Status
Similar threads
- Question