From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 06:56:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DC00106564A for ; Mon, 23 Jun 2008 06:56:52 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id E25F78FC1B for ; Mon, 23 Jun 2008 06:56:51 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 25F47211EC; Mon, 23 Jun 2008 09:56:50 +0300 (EEST) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24787-06; Mon, 23 Jun 2008 09:56:49 +0300 (EEST) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 2FB5B211EB; Mon, 23 Jun 2008 09:56:49 +0300 (EEST) Message-ID: <485F4930.601@bulinfo.net> Date: Mon, 23 Jun 2008 09:56:48 +0300 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Ivan Voras References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu> <20080620140623.GC83165@rink.nu> In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-stable@freebsd.org Subject: Re: Incorrect file size? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 06:56:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Ivan Voras wrote: > Rink Springer wrote: >> On Fri, Jun 20, 2008 at 03:54:22PM +0200, Ivan Voras wrote: >>> Except that the file in question should be, judging by the filename, a >>> simple text file. I don't really see how a whitelist could grow to such >>> monstrous sizes :) Most likely it's a file system corruption - fsck >>> should be the first thing to try. >> The 'vscan' user leads me assume this is SpamAssassin - I've seen this >> behaviour at work, where our scripts were trying to backup a 1TB file >> (which actually was ~vscan/.spamassassin/auto-whitelist). The result was >> that the backup script died due to lack of disk space on the backup >> server (as we don't use compression). Yes, it is SpamAssassin and I have the same problem with the backups. The Amanda complains with: xxxxxxxxxxx / lev 1 FAILED [dump larger than available tape space, 307256178 KB, skipping incremental] yyyyyyyyyyyy / lev 4 FAILED [dump larger than tape, 354005617 KB, skipping incremental] I don't think this is a file system corruption because there are no reasons for this. Also I have seen this on different machines. Any ideas how to fix this? >> >> When I was investigating why the file could be so large it, it turned >> out the file was only a few hunderd 'real' MB's, so that is why I assume >> this person is having the same issue as we do. The file is a Berkeley DB >> file, by the way, so there's nothing textfile about it ;-) > > I learn something every day :) > Didn't know BDB was smart enough to create sparse files. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFIX0kwxJBWvpalMpkRAjkaAKCbF7sylsDyI2umCAoneqBqAYCNqwCgnQjA 9FkgJiVhqNI2NGCAlWpqfbg= =PQZ1 -----END PGP SIGNATURE-----