Quote:
Originally Posted by
bakunin
One possibility is that the directory is NFS-mounted, as era has already mentioned. Another possiblity would be a process that writes to this directory. Suppose a process that writes more or less constantly to a file, something like "vmstat 1 > /some/file" if you now remove "/some/file" ls will not show it, but it will still be there as long as the process (vmstat in this example) runs. You can see that by running "df" against the filesystem holding the file.
(btw. this is one excellent method to drive a Sysadmin crazy: Fill up the /tmp filesystem with such a mechanism and use a sufficiently innocent processname. No, do NOT try this on your colleague. ;-)) )
Use a tool like "fuser" to determine processes which still write to the filesystem/directory to remedy such a situation. Once you kill the process the filespace becomes available at once as the respective i-node is released automatically.
I hope this helps.
bakunin
The /home directory is mounted as JFS. It a partition on a local drive.
I tried fuser with some flags but did not get any useful information back.
bash-3.00# pwd
/home/spark/old/sp2f941
bash-3.00# fuser -d *
BUILD:
bash-3.00# cd BUILD
bash-3.00# fuser -d *
*: A file or directory in the path name does not exist.
bash-3.00# fuser -dV *
*: A file or directory in the path name does not exist.
bash-3.00# cd ..
bash-3.00# fuser -dV *
BUILD:
bash-3.00# fuser -u /home
/home:
bash-3.00#
Did I do the correct parameters?
here is the full results from mount.
bash-3.00# mount
node mounted mounted over vfs date options
-------- --------------- --------------- ------ ------------ ---------------
/dev/hd4 / jfs Feb 07 16:55 rw,log=/dev/hd8
/dev/hd2 /usr jfs Feb 07 16:55 rw,log=/dev/hd8
/dev/hd9var /var jfs Feb 07 16:55 rw,log=/dev/hd8
/dev/hd3 /tmp jfs Feb 07 16:55 rw,log=/dev/hd8
/dev/hd1 /home jfs Feb 07 16:56 rw,log=/dev/hd8
/proc /proc procfs Feb 07 16:56 rw
/dev/hd10opt /opt jfs Feb 07 16:56 rw,log=/dev/hd8
bash-3.00#