-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver Fromme wrote:
Ivan Voras wrote:
Rink Springer wrote:
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
-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
On Mon, Jun 23, 2008 at 09:56:48AM +0300, Krassimir Slavchev wrote:
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?
Either use backup software that is aware of sparse files
or
On Mon, Jun 23, 2008 at 09:56:48AM +0300, Krassimir Slavchev wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Chadwick wrote:
On Mon, Jun 23, 2008 at 09:56:48AM +0300, Krassimir Slavchev wrote:
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
On Mon, Jun 23, 2008 at 12:19:28AM -0700, Jeremy Chadwick wrote:
I've used SpamAssassin for a few years now, and I've never seen this
happen (including during migration from RELENG_6 to RELENG_7, and
between SpamAssassin versions (from 3.0 to 3.2.x). I cannot even begin
to imagine how that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello All,
There is something strange on my mail server running 6.2-STABLE:
# 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
-
On Fri, Jun 20, 2008 at 03:34:26PM +0300, Krassimir Slavchev wrote:
Hello All,
There is something strange on my mail server running 6.2-STABLE:
Bring down the system and force a fsck of your filesystem(s).
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius
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
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
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
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
Ivan Voras wrote:
Rink Springer wrote:
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
On Fri, Jun 20, 2008 at 04:25:05PM +0200, Ivan Voras wrote:
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
14 matches
Mail list logo
