dovecot - Oct 2007 - "Corrupted index cache file" error (Dovecot 1.0.3)

Greetings -

Now that users are beginning to pile up more on our new Dovecot-based  
IMAP service I'm seeing a small number of entries like this in the  
logfiles:

Corrupted index cache file /mailstore/index/o/ozw100/.INBOX/ 
dovecot.index.cache
: invalid record size

We are using Dovecot 1.0.3 with Maildir folders served over NFS from  
NetApp filers, but the index files are stored on local disk.

By "a small number" I mean 4 or 5 on each of our two IMAP servers  
since midnight.

   * Should I be worried?
   * Is there anything I need to do fix the files?  (I'm guessing not  
as no
     problem reports have come in, and the logs show the people affected
     continuing to work throughout the day.)
   * Would upgrading to 1.0.5 help?  (I couldn't see anything in the
     Release Notes for either 1.0.4 or 1.0.5 about this)

Cheers,
Mike B-)

-- 
The Computing Service, University of York, Heslington, York Yo10 5DD, UK
Tel:+44-1904-433811  FAX:+44-1904-433740

* Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

Mike Brudenell wrote:
> Greetings -
> 
> Now that users are beginning to pile up more on our new Dovecot-based
> IMAP service I'm seeing a small number of entries like this in the
> logfiles:
> 
> Corrupted index cache file
> /mailstore/index/o/ozw100/.INBOX/dovecot.index.cache
> : invalid record size
> 
> We are using Dovecot 1.0.3 with Maildir folders served over NFS from
> NetApp filers, but the index files are stored on local disk.
> 
> By "a small number" I mean 4 or 5 on each of our two IMAP servers
since
> midnight.
> 
>   * Should I be worried?
Probably not.
>   * Is there anything I need to do fix the files?  (I'm guessing not as
no
>     problem reports have come in, and the logs show the people affected
>     continuing to work throughout the day.)
I think they probably fix themselves. You could check to see if the same
file occurs more than once. If so, I'd try deleting the cache files
while the user is disconnected (or at least not having that folder open).
>   * Would upgrading to 1.0.5 help?  (I couldn't see anything in the
>     Release Notes for either 1.0.4 or 1.0.5 about this)
Possibly, but we still get occassional index errors too (just one today,
plus four assertion failures in mail_index_view_sync_end). We're on
1.0.5 with mboxes.

Chris

-- 
--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-
Christopher Wakelin,                           c.d.wakelin at reading.ac.uk
IT Services Centre, The University of Reading,  Tel: +44 (0)118 378 8439
Whiteknights, Reading, RG6 2AF, UK              Fax: +44 (0)118 975 3094

On Fri, 2007-10-05 at 17:40 +0100, Mike Brudenell wrote:
> Corrupted index cache file /mailstore/index/o/ozw100/.INBOX/ 
> dovecot.index.cache
> : invalid record size
All cache file errors are completely transparent to clients. The cache
file gets deleted and Dovecot creates the wanted data from scratch.
> We are using Dovecot 1.0.3 with Maildir folders served over NFS from  
> NetApp filers, but the index files are stored on local disk.
I haven't seen these in my stress tests for a long time. So unless you
can figure out a way to reproduce this, I don't think I can do anything
about these for now. Maybe v1.1 has already fixed them. :)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20071006/33a02f89/attachment-0002.bin>