Date: Sun, 11 Jan 2004 10:53:43 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Martin Jessa <freebsd@yazzy.org> Cc: freebsd-current@freebsd.org Subject: Re: File system b0rked. Message-ID: <20040110235343.GB60996@server.vk2pj.dyndns.org> In-Reply-To: <20040111001012.7ea22a1e.freebsd@yazzy.org> References: <20040109203839.GK5994@freepuppy.bellavista.cz> <20040111001012.7ea22a1e.freebsd@yazzy.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 11, 2004 at 12:10:12AM +0100, Martin Jessa wrote: >Something is totally b0rken. My file system was filled up by a far >too big log file. I deleted it and waited half an hour for system to >"settle down". This is what it still showed: > > >[root@urukhai:/var/log]# du -hs /var/ >471M /var/ > > >[root@urukhai:/var/log]# df -h |grep var >/dev/ad0s1g 1.9G 1.8G -1.5M 100% /var Files in Unix don't have to have names. It is possible to delete an open file and the filename will go away but the file will remain (still occupying space) until it is closed. The easiest way to identify the process would be to run "lsof /var" and look for an entry without a filename. You then need to either kill the process or send it whichever signal it needs to tell it to switch to a new logfile. (If you don't have lsof installed, it may be possible to identify the process from the filename - it's most likely to be syslogd). Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040110235343.GB60996>