From owner-freebsd-fs@FreeBSD.ORG Fri Oct 15 22:44:27 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 756B21065673 for ; Fri, 15 Oct 2010 22:44:27 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id F2B358FC20 for ; Fri, 15 Oct 2010 22:44:26 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1P6t0h-0001yO-Su for freebsd-fs@freebsd.org; Sat, 16 Oct 2010 00:44:23 +0200 Received: from cpe-24-210-63-182.columbus.res.rr.com ([24.210.63.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 Oct 2010 00:44:23 +0200 Received: from dsamms by cpe-24-210-63-182.columbus.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 Oct 2010 00:44:23 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: David Samms Date: Fri, 15 Oct 2010 18:44:08 -0400 Lines: 33 Message-ID: References: <201010151909.o9FJ9cZf065459@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cpe-24-210-63-182.columbus.res.rr.com User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.10) Gecko/20100630 Thunderbird/3.0.5 In-Reply-To: <201010151909.o9FJ9cZf065459@lurza.secnetix.de> Subject: Re: ZFS trouble: unbelievably large files created X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2010 22:44:27 -0000 On 10/15/10 15:09, Oliver Fromme wrote: > > ls -kls shawxp/var/amavis/.spamBAD > > total 13352131 > > 771 -rw------- 1 110 110 684032 Oct 15 12:02 > > auto-whitelist > > 1 -rw------- 1 110 110 40 Oct 15 12:37 bayes.lock > > 1284 -rw------- 1 110 110 1294336 Oct 15 12:38 bayes_seen > > 4229 -rw------- 1 110 110 4227072 Oct 15 12:38 bayes_toks > > 5025103 -rw------- 1 110 110 553184002048 Oct 15 12:38 > > bayes_toks.expire3515 > > 8320745 -rw------- 1 110 110 140743122878464 Oct 15 12:14 > > bayes_toks.expire97254 > > Ok, so those files are so-called "sparse" files, i.e. they > contain holes that don't actually occupy disk space. > > The numbers in the first column indicate the amount of > physical disk space allocated (in KB). That's about 5 GB > for the first file and 8 GB for the second (this is also > consistent with the "total" value in the first line of the > ls output, i.e. about 13 GB). > > That's still quite big, but certainly not in the TB range. > I do not know why amavis creates such large sparse files, > though. Under UFS I don't observe amavis creating the sparse files. The problem is fairly repeatable, not on demand, but occurs several times a day. High disk activity is a sure sign amavis is creating large files. Task shuts down normaly and cpu load is low. This is a production server but I have moved all critical customer jails back to UFS so can do testing if anyone has any ideas of what to look for.