Hello, from time to time we have this type of problem during the nightly cyr_expire:
Feb 10 04:01:50 mailbackend-4 cyrus-backend/cyr_expire[15569]: IOERROR: user.<username> zero index/expunge record 299/301 Feb 10 04:01:50 mailbackend-4 cyrus-backend/cyr_expire[15569]: failure expiring user.<username>: System I/O error Feb 11 04:01:48 mailbackend-4 cyrus-backend/cyr_expire[2010]: IOERROR: user.<username> zero index/expunge record 299/301 Feb 11 04:01:48 mailbackend-4 cyrus-backend/cyr_expire[2010]: failure expiring user.<username>: System I/O error Feb 12 04:02:19 mailbackend-4 cyrus-backend/cyr_expire[27580]: IOERROR: user.<username> zero index/expunge record 299/301 Feb 12 04:02:19 mailbackend-4 cyrus-backend/cyr_expire[27580]: failure expiring user.<username>: System I/O error Feb 13 04:03:15 mailbackend-4 cyrus-backend/cyr_expire[19753]: IOERROR: user.<username> zero index/expunge record 299/301 Feb 13 04:03:15 mailbackend-4 cyrus-backend/cyr_expire[19753]: failure expiring user.<username>: System I/O error This leaves cyrus.*.NEW files in the mailbox directory of the user and requires a reconstruct. What's behind? And how can we avoid this problem? --Frank Elsner ---- 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
