Date: Thu, 15 Jan 1998 11:21:45 -0800 From: Jonathan Hahn <hahn@and.com> To: freebsd-questions@FreeBSD.ORG, ghunt@emx.ca Subject: Re: Updating Free Block List Message-ID: <199801151921.LAA03453@and.com>
next in thread | raw e-mail | index | archive | help
The *space* for a unix file is deallocated when there are zero references to the file from the file system (i.e. links) AND zero references from programs (i.e. open file descriptors). This sounds like all file system references to one or more tmp files have been removed, but one (or more) programs still has the file(s) open. This would prevent the space from being deallocated. Such a file is not in the file system and would not be visible to du. There used to be a program called ncheck which would dump all the existing files and their paths. It's no longer in the distribution, but maybe there's a replacement? -jon > From owner-freebsd-questions@freebsd.org Thu Jan 15 10:55:11 1998 > From: "Glenn Hunt" <ghunt@emx.ca> > Organization: EMX Enterprises Limited > To: freebsd-questions@freebsd.org > Subject: Updating Free Block List > > I am running 2.2.5-RELEASE on a Pentium 100, 40MB RAM, 1GB IDE HDD > as a firewall. On my /var filesystem, temp files are created and > deleted, but when they are deleted, the free block list is not > updated. If I use 'df', it will say that there are 5,100 blocks > used, but when I run 'du' in the /var directory, it only shows 3,000 > block used. The number using 'df' seems to continue to grow, until > eventually it thinks the filesystem is full, and it stops accepting > mail, etc. Only a reboot solves this problem. What am I missing. I > have compiled the standard kernel, except that I have configured an > extra network card. > > Glenn Hunt > ghunt@emx.ca >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801151921.LAA03453>