Re: Moving mailboxes from CIMAP-2.3.16 to CIMAP-3.0.5

2018-05-08 Thread Niels Dettenbach via Info-cyrus
Am Montag, 7. Mai 2018, 22:26:19 CEST schrieb James B. Byrne via Info-cyrus:
> I have tried moving things over using imapsync-1.836 and while this
> appears to work we end up with vastly enlarged user mailbox sizes.
> Also I cannot see the quota setting for most users although a few are
> reported.
Did you checked / compared file sizes in the mailboxes - i.e. of single mails 
and cyrus.* files? Possibly this is file system related (i.e. max number of 
inodes or block size etc.) under the FeeBSD system (which filesystem do you 
use)?

imapsync works well, if i.e. authenticated by a cyrus admin user (for all 
accounts) in a single transfer. if you faced to problems with timestamps of 
emails in mailclients, you may hace to use "--addheader" to regeneate the 
timestamps from the mails during tansfer. 

But before you start to migrate mailbox contents you have to migrate the 
cyrus databases - i.e. mailboxlist, quotas.db etc.) - this usually means 
exporting / importing mailboxlist, quotas etc. from the regarding database 
files from cyrus.

see i.e.:
https://www.cyrusimap.org/docs/cyrus-imapd/2.4.7/internal/database-formats.php

rsync is difficult as the cyus.* files in the mailboxes may be binary or API 
incompatible and the cyus partitioning / storage directoy layout has to be 
the same on the new system. Even filesystem diferences aspects could make 
trouble.

If you have sieve, you have to sync the sieve pool by i.e. rsync, but have to 
make shure the diectoy layout is the same and "refresh" the sieve pool then.

 
> I then restarted the process and used rsync natively with --hard-links
> in order to see if that reduced the disc space. Following the rsync of
> all the user mailboxes I re-initialised

> 
> At a guess this means that all of the user mailbox quota settings are
> gone.  However,  I would expect the usage to be shown. And is there
> not a default quota?
Thee is no "quota" as default in cyus. You have to migrate your quotas 
(quotas.db) before you start to sync mailbox contents.


hth a bit,

good luck,


Niels.

-- 
 ---
 Niels Dettenbach
 Syndicat IT & Internet
 http://www.syndicat.com
 PGP: https://syndicat.com/pub_key.asc
 ---
 







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


CPU usage issue with Append command (cyrus 3.0.6)

2018-05-08 Thread Andrew Nichols via Info-cyrus

Hello,

We've recently upgrade to cyrus 3.0.6 and we've been experiencing issue 
where imapd will get stuck in an Append and take 100% CPU time.  The 
client doesn't see anything weird.  I've tried leaving the processes to 
see if they resolve, but they never did.  Doing a kill -TERM twice will 
kill the process.   I did not notice any issues with cyrus 3.0.5, but 
we've been trying to get Xapian indexing going, so we moved to 3.0.6.


Does anyone have any information on where I can look to rectify this 
issue?



Here's an example of the ps output:

87556 cyrus 1 102 0 163M 24192K CPU7 7 1:56 96.71% imapd: imap: hostname> []  user.. Append 
(imapd)
89680 cyrus 1 102 0 163M 24280K CPU4 4 3:10 96.22% imapd: imap: hostname> []  user.. Append 
(imapd)
43932 cyrus 1 102 0 161M 23416K CPU5 5 1:41 96.17% imapd: imap: hostname> []  user.. Append 
(imapd)
81590 cyrus 1 102 0 163M 24976K CPU6 6 3:14 94.76% imapd: imap: hostname> []  user.. Append 
(imapd)


--
Andrew Nichols
Quadrant Newmedia
and...@quadrant.net
306.664.9100

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