Switched to the large files binaries. Every mailbox look sane and new ones can be created. The only strange effect is that running squatter I had many new reindexing I didn't have before. Comparing the manual run with the last log, looks like many folders were not considered before. Any idea? ---------------------------------------------------------------------------------------- Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon Da: Gabriele Bulfon A: info-cyrus@lists.andrew.cmu.edu Data: 13 aprile 2017 12.21.35 CEST Oggetto: Cyrus 2.4.12 illumos and large files Hi, I have some installations of Cyrus 2.4.12 built on our XStreamOS/illumos distro. The source tree was built some time ago, without large files support (-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64). Now that we're moving zfs pools to new systems, these get larger and larger. What happens is that when the available space is larger than 2TB, cyradm cannot create mailboxes causing strange errors. I could verify that rebuilding the same source tree with "-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" and installing on a test machine, everything starts to work again. My question is : can I safely install the new binaries on systems with existing mailboxes? Thanks for any help, Gabriele ---------------------------------------------------------------------------------------- Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon ----Cyrus Home Page: http://www.cyrusimap.org/List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/To Unsubscribe:https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
