From owner-freebsd-questions@FreeBSD.ORG Tue Jul 5 22:31:37 2011 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 2E2EC106566C for ; Tue, 5 Jul 2011 22:31:37 +0000 (UTC) (envelope-from Lowell@Be-Well.Ilk.Org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.39]) by mx1.freebsd.org (Postfix) with ESMTP id 0971C8FC12 for ; Tue, 5 Jul 2011 22:31:36 +0000 (UTC) Received: (qmail 23330 invoked from network); 5 Jul 2011 22:31:36 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Jul 2011 22:31:36 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.8]) by be-well.ilk.org (Postfix) with ESMTP id 60C4E5C60; Tue, 5 Jul 2011 18:31:29 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 4861B39847; Tue, 5 Jul 2011 18:31:27 -0400 (EDT) From: Lowell Gilbert To: Yuri References: <4E1367E7.3050205@rawbw.com> Date: Tue, 05 Jul 2011 18:31:27 -0400 In-Reply-To: <4E1367E7.3050205@rawbw.com> (yuri@rawbw.com's message of "Tue, 05 Jul 2011 12:37:11 -0700") Message-ID: <44r564jr5s.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: FreeBSD Questions Subject: Re: Tool to show the recent disk space consumers? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2011 22:31:37 -0000 Yuri writes: > I hit this problem periodically when a lot of disk space is gone and > it's hard to tell where did it go. Once it was thunderbird writing > huge index file as a consequence of some bug, on another occasion it > was the bug in KDE writing some huge index somewhere in ~/.kde4. > > Is there a tool slowly indexing the file system and showing where > exactly did the sudden growth of consumed space occur? > > I know about du(1) but I am looking for some program that can detect > the dynamics and pinpoint the offending files. A quick-and-rough approach that I sometimes use is to look at the incremental backups...