If you can not identify the process that is holding a file open, then a reboot will help as that will close all running processes (and so close all open files).Īnother consideration is filesystem corruption. If a file that has been deleted is still open by a process, the space will not be reclaimed until the process closes the file (or is killed). proc/14024/task/14024/fdinfo/4': No such file or directory du:Ĭannot access /proc/14024/fd/4': No such file or directory du: cannotĪccess/proc/14024/fdinfo/4': No such file or directoryįilesystem Size Used Avail Use% Mounted on The only thing I can think of is a log file that was deleted while applications append to it.ĭisk space usage is slowly but continuously rising towards full capacity (~1k/min with very small decreases from time to time)ĭu: cannot access /proc/14024/task/14024/fd/4': No such file or directory du: cannot access
Running as root on an Amazon Linux AMI (seems like Centos), lots of free memory available, no swapping going on, no apparent file descriptors issue. How come os shows 6.5G used but I see only 3.6G in files/directories?
0 kommentar(er)
