[Dovecot] dotlock timestamp trouble

Giorgenes Gelatti giorgenes at gmail.com
Fri Jan 23 15:29:55 EET 2009


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 <giorgenes at gmail.com>

> 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 differences of 120 and 60 seconds.
>
> Thanks for the reply,
> gpg
>
> 2009/1/20 Timo Sirainen <tss at iki.fi>
>
> 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 they all
>> 120 seconds?
>>
>> > I'm using dovecot 1.1.6 over NFS.
>> > Any thoughts?
>>
>> What OS are you using on the NFS clients? Perhaps this is a caching
>> issue, have you tried changing/disabling attribute cache timeouts?
>>
>
>


More information about the dovecot mailing list