On 03/12/2012 09:22 AM, Jeroen van Meeuwen (Kolab Systems) wrote:
We are pleased to announce the release of Cyrus IMAPd 2.4.14.This is a stable release in the 2.4.x series. The release mainly contains bug fixes, mostly small but significant. Please find an overview of all bugs resolved in this release at: http://www.cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.14 You can download via HTTP or FTP: http://cyrusimap.org/releases/cyrus-imapd-2.4.14.tar.gz ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.14.tar.gz Kind regards, Jeroen van Meeuwen ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
I just updated my replication server from 2.4.12 to 2.4.14 and then got nothing but "System I/O error" errors in the logs. I took a look at http://bugzilla.cyrusimap.org/show_bug.cgi?id=3381 and noticed this:
You can convert your mail directory hashing scheme from 32bit fulldirhash to 64bit fulldirhash with following commands: % tools/rehash basic % tools/rehash fullUnfortunately I have almost 5TB of mail spread out on 23 different mount points. All the letters in /imap/mail are individual mount points so rehashing would mean lots of moves across the mount points which won't be quick.
Is there a way to force Cyrus to use the old 32bit way, other than just removing the patch?
<<attachment: boutilpj.vcf>>
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
