On 2014-02-05 10:09, Phil Pennock wrote:

Well-behaved long-running programs don't hold open unlinked files for
any length of time.

Exactly my point.


Then I ask the filesystem how full it is, with "df", which is a quick
metadata query; I'll probably use "df -hi" to get human-readable figures
and inode usage too (though -h is not completely portable).  If df says
the filesystems are not full, then I move onto another line of enquiry
without impacting a running system by hitting a large chunk of the
filesystem tree.  If df says a filesystem is full, then I might use du
and lsof to trace down where the consumption is (with some short-cut
mental heuristics for common cases, such as syslog and /var and crappy
log-rotation programs).

Yes, df is good to identify which filesystem is full, but du is expensive, but great to pinpoint which directory, which user or process is taking up all the space.


Can you provide specific examples of applications using unlinked files
in a way which you feel is erroneous, without it being a sign of an
application bug?

mysqld, firefox, dropbox, tunderbird, and some more processes all have open deleted files, and they stay open until the apps is shutdown.


--
Yves.
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/

Reply via email to