Hi All,
after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of messages about corrupted index files in the syslog ("Error: Corrupted transaction log" and "Warning: fscking index file .. dovecot.index".
I tried flock and even dotlock, but the problems persist.
The system is a VPS with an overlay filesystem which did work flawlessly with the old dovecot install and is not reporting any errors in the host machine.
From time to time I get warnings about an exceeded inotify limit for the dovecot user - might this be a problem? Anybody has an idea what might be the cause those problems and how to track them down.
Oliver
-- Protect your environment - close windows and adopt a penguin!
Hi List,
Am 21.01.2015 um 13:24 schrieb Oliver Welter:
Hi All,
after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of messages about corrupted index files in the syslog ("Error: Corrupted transaction log" and "Warning: fscking index file .. dovecot.index".
I tried flock and even dotlock, but the problems persist.
The system is a VPS with an overlay filesystem which did work flawlessly with the old dovecot install and is not reporting any errors in the host machine.
From time to time I get warnings about an exceeded inotify limit for the dovecot user - might this be a problem? Anybody has an idea what might be the cause those problems and how to track them down.
Some more debugging - I did a "fuser" on a broken dovecot.index file and see a lot of stale file handles, looks like something is not cleaning up. Any ideas are still welcome....
Oliver
-- Protect your environment - close windows and adopt a penguin!
Oliver Welter:
after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of messages about corrupted index files in the syslog ("Error: Corrupted transaction log" and "Warning: fscking index file .. dovecot.index".
Some more debugging - I did a "fuser" on a broken dovecot.index file and see a lot of stale file handles, looks like something is not cleaning up. Any ideas are still welcome....
if your using classic maildir format I would try to completly remove any dovecot index files.
my guess: the existing index files are /so old/ dovecot is unable to repair them in a propper way.
Andreas
Hi Andreas,
Am 25.01.2015 um 12:41 schrieb Andreas Schulze:
Oliver Welter:
after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of messages about corrupted index files in the syslog ("Error: Corrupted transaction log" and "Warning: fscking index file .. dovecot.index".
Some more debugging - I did a "fuser" on a broken dovecot.index file and see a lot of stale file handles, looks like something is not cleaning up. Any ideas are still welcome....
if your using classic maildir format I would try to completly remove any dovecot index files.
my guess: the existing index files are /so old/ dovecot is unable to repair them in a propper way.
I already removed them (when they broke) but the problem comes up again
- it seems to be an issue with concurrent mailbox access and locking but I am unable to track it down further. It would be helpful to know what changed in the handling of locks/indexes from 1.1 to 2.2....
Oliver
-- Protect your environment - close windows and adopt a penguin!
Am 25.01.2015 um 12:45 schrieb Oliver Welter:
Hi Andreas,
Am 25.01.2015 um 12:41 schrieb Andreas Schulze:
Oliver Welter:
after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of messages about corrupted index files in the syslog ("Error: Corrupted transaction log" and "Warning: fscking index file .. dovecot.index".
Some more debugging - I did a "fuser" on a broken dovecot.index file and see a lot of stale file handles, looks like something is not cleaning up. Any ideas are still welcome....
if your using classic maildir format I would try to completly remove any dovecot index files.
my guess: the existing index files are /so old/ dovecot is unable to repair them in a propper way.
I already removed them (when they broke) but the problem comes up again
- it seems to be an issue with concurrent mailbox access and locking but I am unable to track it down further. It would be helpful to know what changed in the handling of locks/indexes from 1.1 to 2.2....
As Follow-Up for archive readers - I dont know what the root cause was, but moving the maildirs from overlayfs to a dedicated non-overlayfs partition solved the problem.
Oliver
-- Protect your environment - close windows and adopt a penguin!
participants (2)
-
Andreas Schulze
-
Oliver Welter