Hi,
At first I would like to strongly un-recommend you to do the "fuser -ck /tmp" !!
This will kill all open processes in /tmp, i.e. it will kill your system.
The best you can do is a "fuser -cu /tmp", This will tell you the current processes open in /tmp.
The reason for your error is that someone has removed a file while a process still had the file open for writing. Therefor always first check a file before deleting it, escpecialy when residing in /tmp. You can do this using "fuser -fu /tmp/
".
Ok, what to do :
- bdf /tmp
- cd /tmp; du -ks .
These two should differ a lot (df counts, bdf looks up free space).
If so, do the "fuser -cu /tmp" to see all the current open processes in /tmp. ps -ef | grep all of them to see if this could be your file. When killing the right process bdf immediatly shows you the correct free space.
Of course you can compare this again with "df-ks .".
Never delete a file in /tmp without checking the file first with "fuser -fu /tmp/
And if the file is in use, but has to be deleted, then always use : "> /tmp/"
This will only zero the file and will not change the inode, etc.
Good luck !!
Regs David
@yourservice
