Date: Thu, 29 Jun 2000 08:20:07 -0400 From: "Troy Settle" <troy@picus.com> To: <freebsd-questions@freebsd.org> Subject: RE: Where is the disk pace? Message-ID: <FCEELIAEIIECDGKKJLMIEEEGCAAA.troy@picus.com> In-Reply-To: <200006291030.LAA08370@ngo.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Gods, this happens so often to so many people. I've been forced to reboot a server a couple times because of this [bug|feature]. I was told that this is the way it is, and that there was no room for discussion. I'd really like to know what would be so hard about having the kernel kick back a message of "permission denied: file open by process xxx" when someone or something tries to unlink an open file. This would make life so much easier for so many people, and it couldn't possibly be too difficult to implement in the same portion of code that prevents the unlinking of files by checking the flags. -- Troy Settle Network Analyst Picus Communications 540.633.6327 ** -----Original Message----- ** From: owner-freebsd-questions@FreeBSD.ORG ** [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Mac ** Sent: Thursday, June 29, 2000 6:30 AM ** To: Rafael A. Reta Rodriguez ** Cc: freebsd-questions@freebsd.org ** Subject: Re: Where is the disk pace? ** ** ** > > > # cd /var/log ** > > > # du -k ** > > > 2638 . ** > > > # df -k ** > > > Filesystem 1K-blocks Used Avail Capacity Mounted on ** > > > /dev/wd0s1d 19815 14094 4136 77% /var/log ** > > > ** > > > ** > > > du says that I have 2,638K and df says 14,094K used... ** What is grong ** ** The classic cause of this is a large file that's been deleted (so it ** doesn't show up in directory listings (or 'du')) but the file's still ** open and being used by a process somewhere, so the kernel ** doesn't delete ** it. ** ** Once the process has closed the file, then it will be removed ** altogether and the disk blocks freed up. ** ** ** One possible cause of this could be some program or other that's ** rotating log files, but the process doing the logging hasn't ** let got of ** the old file yet. ** ** If you can umount /var/log then the problem will dissapear, ** as it will ** if you kill all processes using files on /var/mail. (anyone ** know how you ** find out which processes are uisng files in a mount point?) ** ** One other point, is that you _might_ have a corrupt filesystem. ** ** If you do get it umount-ed, then run 'fsck' over it as well ** just to be ** sure. ** ** ** ** ** ** ** Mac ** ** ** To Unsubscribe: send mail to majordomo@FreeBSD.org ** with "unsubscribe freebsd-questions" in the body of the message ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FCEELIAEIIECDGKKJLMIEEEGCAAA.troy>