We are currently cleaning up after a similar analysis. Our current plan is to clean up the sync. dirs on a restart of the sync_client. If there is no advantage to saving state, maybe the sync_server could do this automatically. Cheers, Ken On Mon, Apr 13, 2009 at 09:29:11PM +0200, Michael Glad wrote: > Cyrus being restarted / sync server abending, apparently causes it to > leave sub dirs in the 'sync.' dirs containing hard links to messages. > They currently sum to 40k+ links on one of my replicas :-( . > > I noticed them during an yet unsuccessful attempt to find out why > message body inconsistencies now and then occur > between master and replica. > > The 40k+ entries annoy me and I have a uneasy feeling that they may be > involved in the creating the inconsistencies. > So is there a way to clean up the sync. dirs -- can one just remove > the sub dirs / hard links while the sync server is down? > > -- Michael > > ------------------------ > The inconsistencies seem to arise when a user delete a message, thereby > copying it to a trash folder. > Now and then, this action on the replica nukes a message file owned by > another user on the same cyrus partition, so > that the trash file and the two user mailbox files are now hardlinked > together. > > Environment: 2.3.14 + FM patches as of 2009-03-31 on RHEL 5.3/x86_64. > Single instance store + fast rename + delayed delete + delayed expunge > > > ---- > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
