dovecot - Sep 2005 - Still weird UID ordering issues with maildir

Nightly 20050829 (includes everything currently in nightly/ChangeLog):

Sep  1 09:25:02 server dovecot: imap-login: Login: user=<tv>,
method=PLAIN, rip=192.168.1.1, lip=192.168.1.3, TLS
Sep  1 09:25:02 server dovecot: IMAP(tv): Maildir /home/tv/.maildir sync: UID
< next_uid (1187 < 1188, file = 1125581033.7788_2.server.duh.org:2,)

repeated every time I try to login.  I had to nuke the dovecot indexes and
let it reindex (which throws off the ordering of some messages).  It had
been working without incident since updating to 20050829, until now.

-- 
-- Todd Vierling <tv at duh.org> <tv at pobox.com> <todd at
vierling.name>

On Thu, 1 Sep 2005, Todd Vierling wrote:
> Nightly 20050829 (includes everything currently in nightly/ChangeLog):
>
> Sep  1 09:25:02 server dovecot: imap-login: Login: user=<tv>,
method=PLAIN, rip=192.168.1.1, lip=192.168.1.3, TLS
> Sep  1 09:25:02 server dovecot: IMAP(tv): Maildir /home/tv/.maildir sync:
UID < next_uid (1187 < 1188, file = 1125581033.7788_2.server.duh.org:2,)
>
> repeated every time I try to login.  I had to nuke the dovecot indexes and
> let it reindex (which throws off the ordering of some messages).  It had
> been working without incident since updating to 20050829, until now.
I spoke too soon.  Right after reindexing:

Sep  1 09:30:44 server dovecot: imap-login: Login: user=<tv>,
method=PLAIN, rip=192.168.1.1, lip=192.168.1.3, TLS
Sep  1 09:31:01 server dovecot: IMAP(tv): Maildir /home/tv/.maildir sync: UID
< next_uid (654 < 655, file = 1125581406.14218_2.server.duh.org:2,)

And I had to nuke the indexes again.

-- 
-- Todd Vierling <tv at duh.org> <tv at pobox.com> <todd at
vierling.name>

On Thu, 2005-09-01 at 09:30 -0400, Todd Vierling wrote:
> Nightly 20050829 (includes everything currently in nightly/ChangeLog):
> 
> Sep  1 09:25:02 server dovecot: imap-login: Login: user=<tv>,
method=PLAIN, rip=192.168.1.1, lip=192.168.1.3, TLS
> Sep  1 09:25:02 server dovecot: IMAP(tv): Maildir /home/tv/.maildir sync:
UID < next_uid (1187 < 1188, file = 1125581033.7788_2.server.duh.org:2,)
> 
> repeated every time I try to login.  I had to nuke the dovecot indexes and
> let it reindex (which throws off the ordering of some messages).  It had
> been working without incident since updating to 20050829, until now.
Actually deleting indexes shouldn't matter at all, since Dovecot does
that by itself after writing that error message.

But you're still using it with NFS? Probably somehow related to that..
The error message means that Dovecot saw a message 1187 that wasn't in
index, but index said it already had seen message 1188. Probably means
that the file was temporarily lost in some sync, but later seen again in
another sync.. Dovecot isn't very forgiving if readdir() skips files.

Are there other maildir clients than Dovecot updating the maildir? That
can cause those problems.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20050911/23c518d3/attachment.bin>