Date: Fri, 20 Jun 2008 16:06:23 +0200 From: Rink Springer <rink@FreeBSD.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: Incorrect file size? Message-ID: <20080620140623.GC83165@rink.nu> In-Reply-To: <g3gcqe$qfv$1@ger.gmane.org> References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu> <g3gcqe$qfv$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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). 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 ;-) But still, when in doubt, fsck(8) is sure to aid you. -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080620140623.GC83165>