Charles Marcus wrote:
On 5/23/2008, Knute Johnson (linux@www.knutejohnson.com) wrote:
Any ideas what the problem is or how to fix it?
Output of dovecot -n?
Any additional config parameters? No one here is a mind reader... ;)
Well neither am I. Why didn't you tell me you wanted that before I posted.
No offense intended, but...
I probably read that when I signed up for the list a couple of years ago, but I forgot.
It [should be] a given that basic configuration information will most likely be necessary to help you find a problem... no? At least, thats the way its always been on every support list I've ever been on...
You're right!
Anyway, a quick google finds some hits on this error, so if you had already googled the error (and if you hadn't - shouldn't you have?)...
I didn't have as much luck as you, so thank you for finding the info.
It appears the consensus is, these errors are harmless and don't impact performance, Timo cannot reporoduce them any longer (since post 1.0 release), and he thnks they are fixed in 1.1 version (release imminent).
One thing I saw suggested was to be sure that no client is accessing the affected maildirs, and delete the indexes manually.
I'll give that a try and see what the log says tomorrow.
There is also a suggeston that there may be an issue with NFS/Redhat and certain kernel versions...
Are you using NFS? What version of the Redhat kernel?
No NFS. 2.6.24.7-92.fc8.
Thanks,
--
Knute Johnson linux@www.knutejohnson.com