From owner-freebsd-questions@FreeBSD.ORG Wed Mar 20 23:09:11 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 35B8C5DE for ; Wed, 20 Mar 2013 23:09:11 +0000 (UTC) (envelope-from danny@clari.net.au) Received: from fallbackmx07.syd.optusnet.com.au (fallbackmx07.syd.optusnet.com.au [211.29.132.9]) by mx1.freebsd.org (Postfix) with ESMTP id A5943A1A for ; Wed, 20 Mar 2013 23:09:10 +0000 (UTC) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by fallbackmx07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id r2KN920W028126 for ; Thu, 21 Mar 2013 10:09:02 +1100 Received: from [192.168.100.102] (c114-76-1-137.eburwd4.vic.optusnet.com.au [114.76.1.137]) by mail05.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id r2KN8qti017372 for ; Thu, 21 Mar 2013 10:08:53 +1100 Message-ID: <514A416C.1040706@clari.net.au> Date: Thu, 21 Mar 2013 10:08:28 +1100 From: "Daniel O'Callaghan" User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: "Leaking" disk space References: <20130320170241.278d4fb515536cb6669ae0bf@yahoo.es> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.0 cv=Zs61sKHG c=1 sm=1 a=rXgAR6YtUHgA:10 a=8nJEP1OIZ-IA:10 a=ejE0-8HIAAAA:8 a=ynHq8t7Mvk8A:10 a=t-ZmQhEZvBYsgfOH9kUA:9 a=wPNLvfGTeEIA:10 a=+rVrtY7z3DVyADW7HUk29Q==:117 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Mar 2013 23:09:11 -0000 On 21/03/2013 3:55 AM, Dan Thomas wrote: > Stopping Postgres doesn't fix it, but rebooting does which points at Have you used fstat to identify the big growing file which is taking up the space, and which process has the file open? A file which has been unlinked from all directories won't be seen by du, but it does not free disk space until no process has it open. USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root syslogd 47648 8 / 4317027 -rw-r--r-- 19776 w root syslogd 47648 9 / 4317041 -rw------- 63 w That might help to track it down. Danny