Hi! Today, I ran into a totally new kind of trouble with replication. Apparently, in some situation, when a user has some folders in the DELETED hieararchy, and the folders get actually removed from the disk, and there is a USER operation for that user, the replication code tries to replicate the no-longer-existent folders in DELETED hierarchy and gets errors such as --clip-- Jan 19 10:59:31 pcn2 i16/sync_client[6696]: IOERROR: opening index DELETED.user.<censored>.BIOMEDICUM.Matkat 2012.06-20.Untitled Folder.4F17D602: System I/O error Jan 19 10:59:31 pcn2 i16/sync_client[6696]: IOERROR: Failed to open DELETED.user.<censored>.BIOMEDICUM.Matkat 2012.06-20.Untitled Folder.4F17D602: System I/O error Jan 19 10:59:31 pcn2 i16/sync_client[6696]: Error in do_sync(): bailing out! System I/O error --clip-- As can be seen here, the folder that Cyrus is trying the replicate, is no longer existent in the DELETED hierarchy (or anywhere else, for that matter): --clip-- admin.mappi.helsinki.fi> lm DELETED.user.<censored>.* DELETED.user.<censored>.BIOMEDICUM.Matkat 2012.06-2012 ESHG.Untitled Folder.4F17D617 (\HasNoChildren) admin.mappi.helsinki.fi> --clip-- Any ideas? I didn't see any behaviour like this in the 2.3 series... Yours, -- Janne Peltonen <janne.peltonen@xxxxxxxxxxx> PGP Key ID: 0x9CFAC88B Please consider membership of the Hospitality Club (http://www.hospitalityclub.org) ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
