From owner-freebsd-questions@FreeBSD.ORG Tue Jul 5 21:16:16 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 73CA41065673 for ; Tue, 5 Jul 2011 21:16:16 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by mx1.freebsd.org (Postfix) with ESMTP id 0D1B48FC12 for ; Tue, 5 Jul 2011 21:16:15 +0000 (UTC) Received: by fxe6 with SMTP id 6so5301434fxe.17 for ; Tue, 05 Jul 2011 14:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LrIQE0YqFF1R+s8UnCS69H3wFubkQ8Og5g9RbvQ0WRU=; b=ocA1dAwy1p4lx326tH8xt4LnE5VECTES/u/E0N4GPqcwnoWuU17E8btYwIBDP+ktLW VH6ocxBCpR2P0JHJwf1O83/SC2okHphrGGLWF7MFCyCpP+Bj8UfO23RhWVAeCikSUBu6 O83iMRqzgwNuHby9x9XBijJrWlfixJh891obs= MIME-Version: 1.0 Received: by 10.223.144.136 with SMTP id z8mr12059858fau.31.1309900574815; Tue, 05 Jul 2011 14:16:14 -0700 (PDT) Received: by 10.223.113.129 with HTTP; Tue, 5 Jul 2011 14:16:14 -0700 (PDT) In-Reply-To: <4E1367E7.3050205@rawbw.com> References: <4E1367E7.3050205@rawbw.com> Date: Tue, 5 Jul 2011 16:16:14 -0500 Message-ID: From: Adam Vande More To: Yuri Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 21:16:16 -0000 > > 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 lot of the monitoring applications can do this such as zabbix and opennms, but they don't necessarily monitor file size on every file so I don't know how efficient it would be if it's not integrated into kqueue. One of the security applications such as samhain may be able to do a better job of it. -- Adam Vande More