From owner-freebsd-fs@FreeBSD.ORG Fri Oct 15 19:09:55 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 92D0D106564A for ; Fri, 15 Oct 2010 19:09:55 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0FD018FC13 for ; Fri, 15 Oct 2010 19:09:54 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id o9FJ9ciV065460; Fri, 15 Oct 2010 21:09:53 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id o9FJ9cZf065459; Fri, 15 Oct 2010 21:09:38 +0200 (CEST) (envelope-from olli) Date: Fri, 15 Oct 2010 21:09:38 +0200 (CEST) Message-Id: <201010151909.o9FJ9cZf065459@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG, dsamms@nw-ds.com In-Reply-To: X-Newsgroups: list.freebsd-fs User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Fri, 15 Oct 2010 21:09:53 +0200 (CEST) Cc: Subject: Re: ZFS trouble: unbelievably large files created X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.ORG, dsamms@nw-ds.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2010 19:09:55 -0000 David Samms wrote: > Oliver Fromme wrote: > > What does "ls -kls" report on those files? > > From out side the jail.... That shouldn't matter. > 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. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd In my experience the term "transparent proxy" is an oxymoron (like jumbo shrimp). "Transparent" proxies seem to vary from the distortions of a funhouse mirror to barely translucent. I really, really dislike them when trying to figure out the corrective lenses needed with each of them. -- R. Kevin Oberman, Network Engineer