Hi,
sorry for beeing offtopic but as qmail "nerds" are usually helpful and
skilled, I hope to find an answer her.
I migrated my qmail/dovecot install two weeks ago from dovecot 1.1.7 to
2.2.13, I did also update the OS, but NOT the kernel (its a vserver).
Now, the dovecot.index files break, in the logs I get "Warning: fscking
index file .. dovecot.index" and "Error: Corrupted transaction log".
The result is, that the clients choke and stop to update their postbox
view, making my customers angry.
The system runs using aufs overlayfs inside a linux vserver, which did
the job for almost 10 years without any issue. I suspected file locking
and switched to "dotlock" but the problems are still there. What might
be remarkable - if I do a "fuser" on a broken index file, I see about 10
to 20 stale file handles.
Sorry again for beeing OT - but anybody has an idea on this?
Oliver
--
Protect your environment - close windows and adopt a penguin!
sorry for beeing offtopic but as qmail "nerds" are usually helpful and
skilled, I hope to find an answer her.
I migrated my qmail/dovecot install two weeks ago from dovecot 1.1.7 to
2.2.13, I did also update the OS, but NOT the kernel (its a vserver).
Now, the dovecot.index files break, in the logs I get "Warning: fscking
index file .. dovecot.index" and "Error: Corrupted transaction log".
The result is, that the clients choke and stop to update their postbox
view, making my customers angry.
The system runs using aufs overlayfs inside a linux vserver, which did
the job for almost 10 years without any issue. I suspected file locking
and switched to "dotlock" but the problems are still there. What might
be remarkable - if I do a "fuser" on a broken index file, I see about 10
to 20 stale file handles.
Sorry again for beeing OT - but anybody has an idea on this?
Oliver
--
Protect your environment - close windows and adopt a penguin!