I have a filesystem on AIX 4.3.3 at 100%. I've cleanup under it and removed very large files which should at have made a dent, and yet I stil see it at 100%. I know that in the past I had to unmount and mount the filesystem to fix this. This time I don't have that option, is there another way?
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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Filesystem at 100%; cleanup; still shows 100%
- Thread starter SLathaJ
- Start date
SLathaJ, a
du -ak | sort -n
in the root of the filesystem will tell you the actual size of all files down the directory tree and sort it so the largest sized files is at the end. You might find the offending file there.
I usually use du -sk * | sort -n, which will narrow it down by file and directory and then go from there. An ls -l can be deceiving on the amount of space you will gain by deleting a file.
Check for a core file in the filesystem (cd <filesystem> and then find . -name core).
Also, I seem to recall that in some Unix OS's a runaway process or an inode that can't be released is the offender. I don't know if that happens in AIX.
du -ak | sort -n
in the root of the filesystem will tell you the actual size of all files down the directory tree and sort it so the largest sized files is at the end. You might find the offending file there.
I usually use du -sk * | sort -n, which will narrow it down by file and directory and then go from there. An ls -l can be deceiving on the amount of space you will gain by deleting a file.
Check for a core file in the filesystem (cd <filesystem> and then find . -name core).
Also, I seem to recall that in some Unix OS's a runaway process or an inode that can't be released is the offender. I don't know if that happens in AIX.
fuser -u /myfs
if you rm a file while its open or writting to it the file will go but the process may still be reseving the space.
find the process and kill it or
fuser -k /myfs (if nothig else is using it!)
try a defragfs to update the fs tables and perhaps find the discrepency
if you rm a file while its open or writting to it the file will go but the process may still be reseving the space.
find the process and kill it or
fuser -k /myfs (if nothig else is using it!)
try a defragfs to update the fs tables and perhaps find the discrepency
- Thread starter
- #9
Thank you all for your help. What helped was doing an fuser against the filesystem and checking for processes and killing them. But in one case I needed to also run ipcs -ma and kill any shared memory processes attached. In my case I knew which users would be using that filesystem.
- Status