We're seeing the following sporadically in the log file (single line broken into separate lines for readability):
Corrupted index cache file /home/user/mail/.index/.imap/INBOX/dovecot.index.cache: invalid record size
We're running dovecot-1.0.7-2.fc8. The imap directory is in the user's NFS-mounted /home directory, but doveot is running on the same host as the /home filesystem. There's plenty of disk space and no other significant system problems. The mail index directory we rm'd a week/so ago, so doveoct has had the opportunity to rebuild it.
Any ideas on what might be causing this? Is this issue anything to worry about?
thanks.
On 02/02/2008, Gary Funck gary@intrepid.com wrote:
Corrupted index cache file /home/user/mail/.index/.imap/INBOX/dovecot.index.cache: invalid record size
Hi,
First of all, being NFS, I presume the system does not support locking. Might it be an idea to check that the user isn't using two clients at the same time? I found that this became a problem over NFS when a user was using both a webmail interface and a standard client eg Thunderbird on the same account.
Where does Dovecot put the INDEX? My problem disappeared as soon as I set INDEX=MEMORY.
Kind regards, Ronald.
-- Ronald MacDonald http://www.rmacd.com/ 0777 235 1655
On 02/02/08 12:27:14, Ronald MacDonald wrote:
On 02/02/2008, Gary Funck gary@intrepid.com wrote:
Corrupted index cache file /home/user/mail/.index/.imap/INBOX/dovecot.index.cache: invalid record size
First of all, being NFS, I presume the system does not support locking. Might it be an idea to check that the user isn't using two clients at the same time? I found that this became a problem over NFS when a user was using both a webmail interface and a standard client eg Thunderbird on the same account.
The user is using two clients (Live Mail(tm) and Apple Mail, IIRC), and might have them both running on different computers. His mailbox is also 380 Megs., fyi.
Regarding NFS, although /home is exported via NFS, it is a local ext3 partition on the server where dovecot is running, and dovecot runs only on that server. Mail is delivered locally to /home/$user/mail/inbox via sendmail+procmail. Reading the wiki, this sort of configuration shouldn't cause locking problems.
Where does Dovecot put the INDEX? My problem disappeared as soon as I set INDEX=MEMORY.
Hmmm, didn't know about that option, but see it described here: http://wiki.dovecot.org/MailLocation Does this mean that as long as the dovecot server is long-running that it will cache indexes into local memory? Or is the index kept in memory only for the per-client connection?
Gary Funck wrote:
On 02/02/08 12:27:14, Ronald MacDonald wrote:
Where does Dovecot put the INDEX? My problem disappeared as soon as I set INDEX=MEMORY.
Does this mean that as long as the dovecot server is long-running that it will cache indexes into local memory? Or is the index kept in memory only for the per-client connection?
Only for per connection. Store indexes on local disk if you wish to have persistent indexes but avoid problems with NFS.
Do something like this mail_location = maildir:~/Maildir:INDEX=/var/lib/dovecot/%u
Tomi
On Fri, 2008-02-01 at 18:02 -0800, Gary Funck wrote:
We're seeing the following sporadically in the log file (single line broken into separate lines for readability):
Corrupted index cache file /home/user/mail/.index/.imap/INBOX/dovecot.index.cache: invalid record size
Try if this happens often with stress testing: http://imapwiki.org/ImapTest
Is this issue anything to worry about?
Not really. Those errors are invisible to clients and the cache file gets fixed automatically. More probablematic is if Dovecot doesn't notice that the file is broken and returns garbage to client.
participants (4)
-
Gary Funck
-
Ronald MacDonald
-
Timo Sirainen
-
Tomi Hakala