Date: Fri, 20 Jun 2008 15:54:22 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-stable@freebsd.org Subject: Re: Incorrect file size? Message-ID: <g3gcqe$qfv$1@ger.gmane.org> In-Reply-To: <20080620132833.GB83165@rink.nu> References: <485BA3D2.3090108@bulinfo.net> <20080620132833.GB83165@rink.nu>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Rink Springer wrote: > Hi, > > On Fri, Jun 20, 2008 at 03:34:26PM +0300, Krassimir Slavchev wrote: >> # ls -l >> total 1239702 >> - -rw------- 1 vscan vscan 4398199488512 Jun 20 15:18 auto-whitelist >> - -rw------- 1 vscan vscan 22 Jun 20 15:18 bayes.lock >> - -rw------- 1 vscan vscan 102168 Jun 20 15:18 bayes_journal >> - -rw------- 1 vscan vscan 1099639861248 Jun 20 15:18 bayes_seen >> - -rw------- 1 vscan vscan 21057536 Jun 20 15:18 bayes_toks >> >> but: >> # df -h >> Filesystem Size Used Avail Capacity Mounted on >> /dev/ar0s1a 19G 3.9G 14G 22% / >> ... >> >> # du >> 1239758 . >> >> # mount >> /dev/ar0s1a on / (ufs, local) >> ... > > This is most likely due to the use of 'sparse files': sequential file > data that consists of only zeros doesn't need have actual storage > associated to it. This is quite normal in UNIX environments, and quite > harmless. 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. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIW7aOldnAQVacBcgRAouWAKCLxfKAx9767zfE+lIgFn6rFZ4cawCeLstv Bkqut78WbRLWkrnMbUUq394= =lEs9 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?g3gcqe$qfv$1>