On Jun 9, 2009, at 6:40 AM, Jonathan Siegle wrote:
But of course there are no problems (well, some very rare random ones
maybe) having multiple processes accessing the same mailbox on the
same
server. Ever since I wrote my imaptest tool (a few years ago?) I've
been
heavily stress testing mu
On Jun 3, 2009, at 12:17 PM, Timo Sirainen wrote:
On Wed, 2009-06-03 at 12:11 -0400, Timo Sirainen wrote:
On Wed, 2009-06-03 at 10:14 -0400, Jonathan Siegle wrote:
On Jun 3, 2009, at 9:35 AM, Timo Sirainen wrote:
On Wed, 2009-06-03 at 09:31 -0400, Jonathan Siegle wrote:
Are you saying that
On Wed, 2009-06-03 at 12:11 -0400, Timo Sirainen wrote:
> On Wed, 2009-06-03 at 10:14 -0400, Jonathan Siegle wrote:
> > On Jun 3, 2009, at 9:35 AM, Timo Sirainen wrote:
> >
> > > On Wed, 2009-06-03 at 09:31 -0400, Jonathan Siegle wrote:
> > >> Are you saying that multiple processes on the same fo
On Wed, 2009-06-03 at 10:14 -0400, Jonathan Siegle wrote:
> On Jun 3, 2009, at 9:35 AM, Timo Sirainen wrote:
>
> > On Wed, 2009-06-03 at 09:31 -0400, Jonathan Siegle wrote:
> >>Are you saying that multiple processes on the same folder(INBOX) on
> >> the same IMAP server can cause this collisio
On Jun 3, 2009, at 9:35 AM, Timo Sirainen wrote:
On Wed, 2009-06-03 at 09:31 -0400, Jonathan Siegle wrote:
Are you saying that multiple processes on the same folder(INBOX) on
the same IMAP server can cause this collision as well? Is there a
difference between running multiple processes
On Wed, 2009-06-03 at 09:31 -0400, Jonathan Siegle wrote:
> Are you saying that multiple processes on the same folder(INBOX) on
> the same IMAP server can cause this collision as well? Is there a
> difference between running multiple processes on the same
> folder(INBOX) on multiple IMA
On Jun 2, 2009, at 1:31 PM, Timo Sirainen wrote:
On Tue, 2009-06-02 at 13:24 -0400, jsie...@psu.edu wrote:
dovecot: IMAP(testuser): Corrupted index cache file /full/path/
dovecot.index.cache: record points outside file
So you're using AIX? Do you also happen to use NFS? Can you
reproduce
On Tue, 2009-06-02 at 13:40 -0400, jsie...@psu.edu wrote:
> > Cache file is the part of Dovecot that demands the most
> > from the OS/filesystem. The most difficult part is probably that it
> > writes to the file without locking. It first reserves a space and then
> > starts writing there. Multiple
On Tue, 2 Jun 2009, Timo Sirainen wrote:
On Tue, 2009-06-02 at 13:24 -0400, jsie...@psu.edu wrote:
dovecot: IMAP(testuser): Corrupted index cache file /full/path/
dovecot.index.cache: record points outside file
So you're using AIX? Do you also happen to use NFS? Can you reproduce
this erro
On Tue, 2009-06-02 at 13:24 -0400, jsie...@psu.edu wrote:
> >> dovecot: IMAP(testuser): Corrupted index cache file /full/path/
> >> dovecot.index.cache: record points outside file
> >
> > So you're using AIX? Do you also happen to use NFS? Can you reproduce
> > this error by running imaptest for
On Tue, 2 Jun 2009, Timo Sirainen wrote:
On Tue, 2009-06-02 at 09:51 -0400, Jonathan Siegle wrote:
I use mbox with mbox-snarf plugin.
I get errors like:
dovecot: IMAP(testuser): Corrupted index cache file /full/path/
dovecot.index.cache: record points outside file
So you're using AIX? Do
On Tue, 2009-06-02 at 09:51 -0400, Jonathan Siegle wrote:
> I use mbox with mbox-snarf plugin.
>
> I get errors like:
>
> dovecot: IMAP(testuser): Corrupted index cache file /full/path/
> dovecot.index.cache: record points outside file
So you're using AIX? Do you also happen to use NFS? Can
I use mbox with mbox-snarf plugin.
I get errors like:
dovecot: IMAP(testuser): Corrupted index cache file /full/path/
dovecot.index.cache: record points outside file
The errors can be in either folders or INBOX.
I put some syslog statements in src/lib-index/mail-cache-lookup.c to
help un
13 matches
Mail list logo
