Therefore such processes may need to be restarted before that file's space will be cleared up on the filesystem. On Linux or Unix systems, deleting a file via rm or through a file manager application will unlink the file from the file system's directory structure however, if the file is still open (in use by a running process) it will still be accessible to this process and will continue to occupy space on disk. To identify the used file size (in blocks), use the command below: # lsof -Fn -Fs |grep -B1 -i deleted | grep ^s | cut -c 2- | awk '' The same reason will cause different disk usage from du command and df command, please refer to Why does df show bigger disk usage than du? proc/25575/fd/33: broken symbolic link to `/oradata/DATAPRE/file.dbf (deleted)' $ echo > /proc/pid/fd/fd_numberįor example, from the lsof output above: $ file /proc/25575/fd/33 Applications may not be designed to deal elegantly with this situation and may produce inconsistent or undefined behavior when files that are in use are abruptly truncated in this manner. This is an advanced technique and should only be carried out when the administrator is certain that this will cause no adverse effects to running processes.
If a graceful shutdown does not work, then issue the kill command to forcefully stop it by referencing the PID.Īlternatively, it is possible to force the system to de-allocate the space consumed by an in-use file by forcing the system to truncate the file via the proc file system.
#Ubuntu clean disk space free
The lsof output shows the process with pid 25575 has kept file /oradata/DATAPRE/file.dbf open with file descriptor (fd) number 33.Īfter a file has been identified, free the file used space by shutting down the affected process. Note: check either the filesystem path within NAME field or the device number under DEVICE to match the filesystem of interest. When you perform a df, the storage shows 90+% utilized, however, there is not really that much written to that space.įirst, obtain a list of deleted files which are still held open by applications: $ lsof | egrep "deleted|COMMAND"ĬOMMAND PID TID TASKCMD USER FD TYPE DEVICE SIZE/OFF NODE NAME The lsof command shows the following output before restarting the java process COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME The file was previously deleted, but only stopping and restarting the jvm/java process released the disk space. The OS was holding several very large log files open with some as large as ~30G.
Why is space not being freed from disk after deleting a file in Red Hat Enterprise Linux?.
0 kommentar(er)
