Date: Fri, 20 Jun 2008 16:25:05 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-stable@freebsd.org Subject: Re: Incorrect file size? Message-ID: <g3gek1$22j$1@ger.gmane.org> In-Reply-To: <20080620140623.GC83165@rink.nu> References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu> <g3gcqe$qfv$1@ger.gmane.org> <20080620140623.GC83165@rink.nu>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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). > > 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. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIW73BldnAQVacBcgRAueCAKDvHyIIKXlCeubk7H4DdyhA76j9SACeLGUc BdGXkCi8uujS2fHqsRUtajg= =y1PG -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?g3gek1$22j$1>