From owner-freebsd-questions@FreeBSD.ORG Fri May 22 16:14:29 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FDEA1065672 for ; Fri, 22 May 2009 16:14:29 +0000 (UTC) (envelope-from LukeD@pobox.com) Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by mx1.freebsd.org (Postfix) with ESMTP id 73D7E8FC1B for ; Fri, 22 May 2009 16:14:29 +0000 (UTC) (envelope-from LukeD@pobox.com) Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 5C0D0B5BFD for ; Fri, 22 May 2009 12:14:28 -0400 (EDT) Received: from lukas.is-a-geek.org (unknown [71.112.210.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id C736CB5BFC for ; Fri, 22 May 2009 12:14:27 -0400 (EDT) Date: Fri, 22 May 2009 09:14:22 -0700 (PDT) From: Luke Dean X-X-Sender: lukas@border.lukas.is-a-geek.org To: freebsd-questions@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Pobox-Relay-ID: A001EE6C-46EB-11DE-90D4-F6BA321C86B1-96347044!a-sasl-fastnet.pobox.com Subject: How to recover disk space after "filesystem full" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Luke Dean List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 16:14:29 -0000 Yes, it sounds like a stupid question, but let me tell the story. The log for my dhcp server filled up /var last night, which meant that dhcpd was also unable to hand out new leases, which meant that I had effectively been DOSed. I'll have to look into changing my logging policies. So, to correct the problem, I log into the router, removed the big log and several other files in /var to free up some space, and assumed this would correct the problem. It did not. Several minutes after freeing up a lot of space on /var, I continued to get "filesystem full" messages and "df" continued to show the capacity at >100%. I checked "df -i" for the inodes too. That was fine. I ran a quick fsck to see if that might shock the system into seeing all the space that I'd freed up, but no good. I ended up rebooting the box. Was there any other possible solution I could've tried? Why wouldn't the free space immediately appear as free?