Problem while deleting mailbox on a private spool on NFS
boutilpj at ednet.ns.ca
Mon Jun 11 07:53:46 EDT 2012
On 06/11/2012 06:15 AM, Arnaud Launay wrote:
> Michael Loftis <mloftis <at> wgops.com> writes:
>> Don't use Cyrus over NFS. It's not safe. You *WILL* end up with corrupt
>> There might be some NFS Client+Server combinations that are safe, but since
>> you've a Linux client I'm guessing your NFS server is also Linux, a known
>> not-safe configuration. The reason is file locking doesn't' really work on
> Is it still current ? I had to move the cyrus spool to an nfs server server due
> to space problems, and I'm getting some of those:
> Jun 11 04:11:53 nw2 imaps: IOERROR: locking index for
> toto.fr!user.coincoin: Unknown code ____ 255
> Linux 3.2 on both client and server, nfs v3.
> If NFS isn't a good answer, what might be ? Problem here is redundancy (the nfs
> server is redundant in a drbd master/slave configuration) and space...
We use iscsi instead of nfs now.
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 286 bytes
Desc: not available
Url : http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20120611/08711aa9/attachment.vcf
More information about the Info-cyrus