Date: Wed, 16 Feb 2000 10:06:40 -0800 From: "John Purser" <johnmpurser@home.com> To: "'VPM Support'" <support@vpm.com>, <freebsd-questions@FreeBSD.ORG> Subject: RE: df/du reporting different results on FBSD3.4 Message-ID: <000d01bf78a8$938a0c80$40390918@vncvr1.wa.home.com> In-Reply-To: <4.2.0.58.20000216085019.01e9b3e0@mail.vpm.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I just installed 3.4 and in two days my 100 meg /var filled up. (With help) I tracked down the offender as /var/log/mgetty.cuaa1, which was mostly full of error messages caused by mgetty reading a config file usr/local/etc/mgetty+sendfax/mgetty.config. This config file is contains over 300 lines of comments which aren't commented out. mgetty tries to read each line and promptly kicks out about three lines of error messages to the log file. It repeats this process every night and after every reboot. After two days mine was gigantic. I moved the file to a larger partition as a temporary fix but the problem is still there. I plan on renaming the config file next and then tracking down what is starting mgetty in the first place. If you find this is your problem too then let me know if you figure out what's starting mgetty or why that config file is written the way it is. Thanks, John Purser -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of VPM Support Sent: Wednesday, February 16, 2000 1:13 AM To: freebsd-questions@FreeBSD.ORG Subject: df/du reporting different results on FBSD3.4 Hi, Strange things are happening that I'm hoping I can get some answer to. I recently upgraded from 3.1 to 3.4. This morning my /var partition (996MB) was at 109% capacity when I did a df. When I did a du -s /var it reported only 68MB. In addition to this I could NOT delete the files and free up any space on the partition. It remain constant or grew. "Something" was writing to the disk and do not know what. A check of running processes (ps -auxww) did not reveal any culprits. As a result of all this mail was not being delivered and for all I know even being received. My resolution was to copy all files over to another partition called /logs which was empty and had 817MB free. I made a new directory called /var1. I then edited the /etc/fstab file to reflect that the /logs partition was now /var and the current /var partition was now /var1 and then rebooted. This solved the immediate problem of no disk space on /var and mail started to flow. Crisis solved for now. But then I issue a du command and a df command and check the space on /var. The results are different. Anyone know why? The results are shown below. bash# du -s /var 67832 /var bash# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 540783 55688 441833 11% / /dev/da1s1f 817743 76710 675614 10% /var /dev/wd0s1f 1504911 655263 729256 47% /u2 /dev/wd1s1e 3789838 2552875 933776 73% /u1 /dev/da1s1e 1215695 884354 234086 79% /usr /dev/da0s1e 996319 1 916613 0% /var1 procfs 4 4 0 100% /proc Thanks, Mark VPM Support support@vpm.com VPM Internet Services (800) 321-0221 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?000d01bf78a8$938a0c80$40390918>