From owner-freebsd-questions@FreeBSD.ORG Fri Mar 22 11:41:58 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A02D8B0C for ; Fri, 22 Mar 2013 11:41:58 +0000 (UTC) (envelope-from godders@gmail.com) Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by mx1.freebsd.org (Postfix) with ESMTP id 67727F55 for ; Fri, 22 Mar 2013 11:41:58 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id bv4so1781221qab.8 for ; Fri, 22 Mar 2013 04:41:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6/bQBTG0kv7lOeZ+9aTj/bhfJMMH0Oz6Fy8fkelE8nU=; b=HvRCIC5A1JIm15fhEx0YBMGDv8Z8+GcU3m5FtQJpnbwJWHmqRkWBqHfxaA/evnFC+2 hNqRKyb1lrdcHero4nvEYbT9Hu73aqscvDQ9takK7Er6BaW1+RHqp4POfsP7o9ZPUWIe uHymycA4UVLcsyJlmAossoxn4Yz5nke+6bYRtE1W5N2xPiuJtQtnRhEPq0G8H0Mft2iQ ZqNTyAKTMBGScY3n5puMkQNZ9Ir88bB7CZzaWVbMrdSQpuyVTunZX+KAtSgYwPCwHY9V mW/Wnl8hlz7I5VArh54kYRztSOHT50XBBcDlQfRDIcvILk+vHA8rxrxy5PHQBMsWMIU+ s4NA== MIME-Version: 1.0 X-Received: by 10.229.61.65 with SMTP id s1mr228909qch.114.1363952512349; Fri, 22 Mar 2013 04:41:52 -0700 (PDT) Received: by 10.49.71.145 with HTTP; Fri, 22 Mar 2013 04:41:52 -0700 (PDT) In-Reply-To: <514B0962.7080606@bananmonarki.se> References: <20130320170241.278d4fb515536cb6669ae0bf@yahoo.es> <514A416C.1040706@clari.net.au> <514B0962.7080606@bananmonarki.se> Date: Fri, 22 Mar 2013 11:41:52 +0000 Message-ID: Subject: Re: "Leaking" disk space From: Dan Thomas To: Bernt Hansson Content-Type: text/plain; charset=ISO-8859-1 Cc: Daniel O'Callaghan , freebsd-questions@freebsd.org 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: Fri, 22 Mar 2013 11:41:58 -0000 > A stab in the dark, but does # sync change anything Alas, no. On 21 March 2013 13:21, Bernt Hansson wrote: > On 2013-03-21 11:40, Dan Thomas wrote: >>> >>> Have you used fstat to identify the big growing file which is taking up >>> the space, and which process has the file open? >> >> >> It's not an unlinked file. I've tried using fstat and lsof to identify >> it, and there's no inodes with zero links or that don't have a >> matching file on disk. > > > A stab in the dark, but does # sync change anything. > > > >> Dan >> >> On 20 March 2013 23:08, Daniel O'Callaghan wrote: >>> >>> 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 >>> >>> >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscribe@freebsd.org" >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> >> >