Looks like bad news. :(
I've run nfstest to look for problems. The output is attached.
I'm not sure, but it looks like a bad nfs environment.
2009/1/25 Timo Sirainen
> 2.6.9 is old and there are several NFS bugs in older 2.6 kernels. So I'd
> try upgrading. I've really no idea what else could b
2.6.9 is old and there are several NFS bugs in older 2.6 kernels. So I'd
try upgrading. I've really no idea what else could be the problem.
On Fri, 2009-01-23 at 11:29 -0200, Giorgenes Gelatti wrote:
> Is there any know issue about it on kernel 2.6.9 (centos)?
> Any other mount options I could try
Is there any know issue about it on kernel 2.6.9 (centos)?
Any other mount options I could try?
Thank you.
2009/1/21 Giorgenes Gelatti
> Dovecot is running on a linux machine (2.6 kernel).
> The nfs was mounted as:
> nfs rw,vers=3,proto=tcp,intr,nolock,noexec,rsize=8192,wsize=8192 0 0
>
> After
Dovecot is running on a linux machine (2.6 kernel).
The nfs was mounted as:
nfs rw,vers=3,proto=tcp,intr,nolock,noexec,rsize=8192,wsize=8192 0 0
After your hint we added the "noac" flag:
nfs rw,vers=3,proto=tcp,intr,nolock,noexec,noac,rsize=8192,wsize=8192 0 0
But the error continues with differe
On Tue, 2009-01-20 at 14:36 -0200, Giorgenes Gelatti wrote:
> Created dotlock file's timestamp is different than current time (1232468644
> vs 1232468524): /path/to/dovecot.index.log
>
> The IT guy swears the clocks are sincronized.
the difference in the above message is exactly 120 seconds. Are
Hi there,
I'm getting a lot of this message in production log:
Created dotlock file's timestamp is different than current time (1232468644
vs 1232468524): /path/to/dovecot.index.log
The IT guy swears the clocks are sincronized.
Whe even have made a test in the machine running dovecot, inside the
