You may be victim of one of the classic UNIX tricks. Create a file, open it and then delete it without closing it. What you now have is an anonymous file, it appears in no directories but has an associated inode. This is extremely useful where you want to create a temporary file that will go away when the process opening it dies or on a reboot.
> -----Original Message----- > From: Geyer, Thomas L. [mailto:[EMAIL PROTECTED]] > Sent: 25 September 2002 16:08 > To: [EMAIL PROTECTED] > Subject: Strange results with DF Command > > > I am running a Linux instance , SLES 7 with the 2.4.17 > kernel. I was in the > process of building gcc-3.2 when my filesystem became full. I > issued the DF > command and the results showed that "/" was at 100%. So I proceeded to > delete the directory that I was building gcc-3.2 in and ran > the DF command > again. There was no change "/" was still at 100%. I proceeded > to delete > additional directories and files and still no change, DF > still reported that > "/" was still at 100%. > > Has anyone else experienced this? What am I missing? > > Thanks in advance for your help. > > Thomas L. Geyer > Email:[EMAIL PROTECTED] > Phone:(330) 471-2073 > Fax:(330) 471-4034 > > > > ********************************************************************** > This message and any attachments are intended for the > individual or entity named above. If you are not the intended > recipient, please do not forward, copy, print, use or disclose this > communication to others; also please notify the sender by > replying to this message, and then delete it from your system. > > The Timken Company > ********************************************************************** > Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons.
