On Sat, 2005-10-22 at 00:40 +0200, Jakob Hirsch wrote:
Jakob Hirsch wrote:
somebody else seeing these?
it seems not.
FWIW, there are other issues. alpha3 had a lot less errors/warnings.
This is still coming all the time: Oct 22 00:03:02 ymmv dovecot: imap(nici): inotify_rm_watch() failed: Invalid argument
I've heard I've broken at least epoll. Maybe inotify went with it?
This seems to be related to lock_method flock, with fcntl it's gone. Deleting the index-files doesn't help.
Oct 22 00:03:03 ymmv dovecot: imap(nici): Lost transaction log file /var/spool/vmail/nici/./Maildir/dovecot.index.log seq 2 Oct 22 00:03:03 ymmv dovecot: imap(nici): Lost transaction log file /var/spool/vmail/nici/./Maildir/dovecot.index.log seq 2 Oct 22 00:19:01 ymmv dovecot: imap(jh): Corrupted transaction log file /var/spool/vmail/jh/./Maildir/dovecot.index.log: Append with UID 5323, but next_uid = 5324 ...
You mean this "Append with UID .. but next_uid" error happens constantly with flock, but not with fcntl? And this isn't NFS-mounted or anything? The error sounds like the locking wouldn't work, but flock should work just as well as fcntl, and with NFS give an error..