[Dovecot] Dovecot reports zero messages erroneously
On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any.
This problem seemed to start happening in alpha3 (and persists in alpha4).
When I revert back to alpha2, the messages show up again.
It looks like a problem with the dovecot.index* files. When I delete them, alpha4 can serve up the mails just fine, and will in fact keep working for a little while. Eventually (within a few hours, although I'm not sure what causes it), dovecot thinks things are empty again.
Like Mark, I'm using Postfix.. I'm not sure if that has anything to do with the problem but I thought it'd be worth pointing out.
If there are any specific things you'd like me to do to try to pin down this problem, let me know.
Chris
On Mon, 2005-10-24 at 09:36 -0700, Chris Spiegel wrote:
On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any.
This problem seemed to start happening in alpha3 (and persists in alpha4).
When I revert back to alpha2, the messages show up again.
Probably because alpha3 contains this change:
* src/lib-storage/index/maildir/maildir-sync.c: We were forcing a
maildir resync when it hadn't changed at all.It looks like a problem with the dovecot.index* files. When I delete them, alpha4 can serve up the mails just fine, and will in fact keep working for a little while. Eventually (within a few hours, although I'm not sure what causes it), dovecot thinks things are empty again.
What about if you do "touch Maildir/new", does it then see the new mails?
What filesystem do you use?
On Friday 28 October 2005 05:27 am, Timo Sirainen wrote:
On Mon, 2005-10-24 at 09:36 -0700, Chris Spiegel wrote:
On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any.
[ ... ]
It looks like a problem with the dovecot.index* files. When I delete them, alpha4 can serve up the mails just fine, and will in fact keep working for a little while. Eventually (within a few hours, although I'm not sure what causes it), dovecot thinks things are empty again.
What about if you do "touch Maildir/new", does it then see the new mails?
Yes, that does cause the new messages to be seen.
What filesystem do you use?
JFS on Linux 2.6.13. I'm just using the default mount options, so no noatime, if that would be an issue.
Chris
On Fri, 2005-10-28 at 23:00 -0700, Chris Spiegel wrote:
On Friday 28 October 2005 05:27 am, Timo Sirainen wrote:
On Mon, 2005-10-24 at 09:36 -0700, Chris Spiegel wrote:
On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any.
JFS on Linux 2.6.13. I'm just using the default mount options, so no noatime, if that would be an issue.
Thought so. I've heard before too that JFS doesn't update directory's mtime when files are added/removed/renamed. Although some people say that mtime is updated with their JFS. Maybe it's somehow configurable? Anyway, that's the problem and I'd rather not add any kludgy workarounds to Dovecot for it.
On Saturday 29 October 2005 03:57 am, Timo Sirainen wrote:
On Fri, 2005-10-28 at 23:00 -0700, Chris Spiegel wrote:
On Friday 28 October 2005 05:27 am, Timo Sirainen wrote:
On Mon, 2005-10-24 at 09:36 -0700, Chris Spiegel wrote:
On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any.
JFS on Linux 2.6.13. I'm just using the default mount options, so no noatime, if that would be an issue.
Thought so. I've heard before too that JFS doesn't update directory's mtime when files are added/removed/renamed. Although some people say that mtime is updated with their JFS. Maybe it's somehow configurable? Anyway, that's the problem and I'd rather not add any kludgy workarounds to Dovecot for it.
Well it's certainly a JFS issue, you're right. JFS does update the mtime when files are created ( via open()/creat() ), removed, and renamed into a directory. However, it doesn't update when a new link is created in a directory, which is of course how maildir delivery works. I'll head on over to the JFS mailing list to get their input.
Thanks, Chris
participants (2)
-
Chris Spiegel
-
Timo Sirainen