'k, this is the second time its happened ... on a file system that is
currently 35% full (52G free), all the disk space disappeared ...
Is there a way of finding out what process is holding open this "immense"
file?
I'm pretty sure lsof can tell you...
either just plain "lsof" or maybe with
At 02:40 PM 7/28/2005, Marc G. Fournier wrote:
'k, this is the second time its happened ... on a file system that is
currently 35% full (52G free), all the disk space disappeared ...
Are you out of inodes? df -i
Is there a way of finding out what process is holding open this "immense"
file?
'k, this is the second time its happened ... on a file system that is
currently 35% full (52G free), all the disk space disappeared ...
Is there a way of finding out what process is holding open this "immense"
file?
Marc G. Fournier Hub.Org Networking Services (http://www.hub