On Tue, Mar 23, 2010 at 03:19:49PM +0200, Timo Sirainen wrote:
I have done some small-scale testing and it looks fine.
Stress testing by running imaptest for same user's same mailbox in 2+
different servers (i.e. two NFS clients reading/writing same mailbox files)
should show up quickly
On Thu, 2010-03-25 at 10:58 +, Brian Candler wrote:
Mar 25 10:22:23 freebsd-dev dovecot: IMAP(br...@dev.example.com): Our dotlock
file /mail/0/6/37/30/brian%dev.example.com/dovecot-uidlist.lock was
overridden (locked 0 secs ago, touched 0 secs ago)
Wonder if dotlock_use_excl=no helps
BTW. the triplicate send was caused by me breaking mailman's permissions
for a while. Hopefully there won't be a fourth mail. :)
signature.asc
Description: This is a digitally signed message part
It's possible that switching the Linux NFS server to a Netapp will help
(which is what it will be deployed onto eventually anyway)
NetApp should help, but I doubt it'll remove all the problems. Also
Dovecot's NFS workarounds work better for Linux NFS client than for
FreeBSD..
I doubt this
On Thu, Mar 25, 2010 at 04:31:56PM +0200, Timo Sirainen wrote:
Mar 25 10:22:23 freebsd-dev dovecot: IMAP(br...@dev.example.com): Our
dotlock file /mail/0/6/37/30/brian%dev.example.com/dovecot-uidlist.lock was
overridden (locked 0 secs ago, touched 0 secs ago)
Wonder if
On Thu, 2010-03-25 at 15:14 +, Brian Candler wrote:
On Thu, Mar 25, 2010 at 04:31:56PM +0200, Timo Sirainen wrote:
Mar 25 10:22:23 freebsd-dev dovecot: IMAP(br...@dev.example.com): Our
dotlock file /mail/0/6/37/30/brian%dev.example.com/dovecot-uidlist.lock
was overridden (locked 0
On 03/25/10 06:58, Brian Candler wrote:
On Tue, Mar 23, 2010 at 03:19:49PM +0200, Timo Sirainen wrote:
I have done some small-scale testing and it looks fine.
Stress testing by running imaptest for same user's same mailbox in 2+ different
servers (i.e. two NFS clients reading/writing same
On Thu, Mar 25, 2010 at 05:25:53PM +0200, Timo Sirainen wrote:
Are you using ext4 on the Linux NFS server?
Yes:
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
Nano/microsecond resolution timestamps fix the worst caching problems.
I can't see whether that's true through stat mtime though.
On Thu, 2010-03-25 at 16:04 +, Brian Candler wrote:
Out of interest, why is dot locking used instead of fcntl here?
My laziness. It's annoying to create different code for locking files
via different ways in different places. (The files are created/written
to in different ways, the locking
On Tue, Mar 23, 2010 at 05:42:02AM -0400, Charles Marcus wrote:
On 2010-03-22 9:31 PM, Stan Hoeppner wrote:
Dovecot has built in locking support for NFS storage.
But it has always been problematic, according to Timo.
Have you got any references on this, apart from
On 23.3.2010, at 13.43, Brian Candler wrote:
I have done some small-scale testing and it looks fine.
Stress testing by running imaptest for same user's same mailbox in 2+ different
servers (i.e. two NFS clients reading/writing same mailbox files) should show
up quickly what kind of errors you
On 03/23/10 07:43, Brian Candler wrote:
On Tue, Mar 23, 2010 at 05:42:02AM -0400, Charles Marcus wrote:
On 2010-03-22 9:31 PM, Stan Hoeppner wrote:
Dovecot has built in locking support for NFS storage.
But it has always been problematic, according to Timo.
Have you got any references on
12 matches
Mail list logo
