This was starting from a clean index, first opening pine on the NFS
Solaris 9 sparc machine, and then at the same time opening pine on my
Fedora 9 i386 workstation.
Why does it matter where you run Pine? Does it directly execute Dovecot
on the local machine instead of connecting via TCP?
On Wed, 2008-06-25 at 12:00 -0400, David Halik wrote:
> I just reproduced the environment and the index corrupted immediately
> across NFS because of the endian issue.
>
> Jun 25 11:53:34 host IMAP(user): : Rebuilding index file
> /dovecot-index/index/user/.INBOX/dovecot.index: CPU architecture
I just reproduced the environment and the index corrupted immediately
across NFS because of the endian issue.
Jun 25 11:53:34 host IMAP(user): : Rebuilding index file
/dovecot-index/index/user/.INBOX/dovecot.index: CPU architecture changed
Jun 25 11:53:35 host IMAP(user): : Corrupted index ca
On Jun 18, 2008, at 9:12 PM, David Halik wrote:
Now this setup is just a test example and not exactly what we'll be
running in production, but it tipped up the problem either way.
Since the index is shared by both the Linux i386 machine and the
sparc64 Solaris machine, if mail is accessed f
When I opened your message, before I could even read it, NFS failed and
corrupted everything. Shades of Shroedinger's Cat!
Just kidding (I hope)
:)
Charles Marcus wrote:
On 6/18/2008, Stewart Dean ([EMAIL PROTECTED]) wrote:
Gee, I've been running for a year now,
Note I said *fully* support
On 6/18/2008, Stewart Dean ([EMAIL PROTECTED]) wrote:
Gee, I've been running for a year now,
Note I said *fully* supported.
Specifically - Timo recommends to use 1.1 if you're using NFS... but by
all means, do what ever you like... :)
--
Best regards,
Charles
Gee, I've been running for a year now, albeit in an NFS environment where there
are only four machines, 3 AIX (A master where the files are resident and 2 other
machines as NFS clients...a mailing list server (which can write heavily to the
mounts) and a login server (which writes lightly if at
Great, I was hoping the answer was to use the 1.1.0 release. I'll let
you know if the issues continue, but that sounds like the problem.
Thanks again,
-Dave
Charles Marcus wrote:
On 6/18/2008, David Halik ([EMAIL PROTECTED]) wrote:
* Linux workstations running Fedora 8/9 i386 and a locally c
On 6/18/2008, David Halik ([EMAIL PROTECTED]) wrote:
* Linux workstations running Fedora 8/9 i386 and a locally called Dovecot 1.0.14
* NFS'd homedir with Maildir setup
* NFS is on Solaris 9 sparcv9 (64bit) running Dovecot 1.0.14
NFS is only fully supported on 1.1+. This is why you're having t
Hi all,
I crawled through the archives for a bit but didn't see anything
helpful, so I apologize if this has already been addressed. We've been
dying to move from Courier to Dovecot across our whole infrastructure
for quite some time, but until recently our setup wasn't possible until
this ha
10 matches
Mail list logo
