Date: Sat, 16 Nov 2002 11:19:57 -0800 From: Kent Stewart <kstewart@owt.com> To: "Paul A. Scott" <pscott@skycoast.us> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: A quizical Message-ID: <3DD69A5D.5070605@owt.com> References: <B9FBD33B.11B86%pscott@skycoast.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul A. Scott wrote: >>/dev/ad0s1e 99183 99068 -7819 109% /var [...] >>Showing /var at 109% capacity, over 99 megs. [...] >>The thing is this ... du feels differently ... [...] >>Little over a meg ... not nearly 100. So the question becomes >>where's the beef? > > > It's possible that some running process has unlinked a file on the /var file > system but still has it open. On UNIX, you can unlink (delete) a file while > it's open to keep it from appearing in the 'ls' and 'du' output, but 'df' > will see the space used. If that's the case here, then when the file is > closed the space will be recovered. I'm not sure what utilities are > available to show which processes have space allocated (I'd sure like to > know of one, though) but if you kill the offending process then the unlinked > file space will be recovered. Easiest solution would be to reboot the > machine, but you would still need to discover the cause or it will happen > again. The port lsof shows open files. Lsof is one of the unique ports because it knows when you have updated your system and haven't rebuilt it. It also tells you that you have forgotten to rebuild it everytime you use it after the system update. > > On the other hand, you might have a different problem. IDK. A "shutdown now" and exit would clean things up with out a complete reboot. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html 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?3DD69A5D.5070605>