On Wed, Sep 10, 2014 at 01:54:08AM +0800, Bret Busby wrote: > The file has (kind of) gone, now (it is no longer accessible, but, > appears to still exist, in the ether of the unknown; still taking up > disc space, whilst, in theory, non-existent),
A file continues to use up disk space until all open file handles are closed. Quite likely Xorg still has the file open, even though you've removed all the hard links (paths) to it on the filesystem. If you still have the system up in the same state, you might see it in /proc/$(pidof Xorg)/fd (or it might be another process other than Xorg, or I might be wrong entirely) > but, when I did briefly examine the contents, hundreds of lines referring to > QPaint problems, were shown. Historically in my experience lots of Qt and KDE programs were extremely verbose on stderr, often because they were built with some debug flag enabled. Depending on the nature of the QPaint messages, this might be the case. Either way, it's probably a severity: minor bug worth reporting if it hasn't already (this bug looks relevant: https://bugs.debian.org/598975 - I guess the thing to do is figure out which program is generating the messages.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140909190858.ga25...@bryant.redmars.org
