Hi I searched the mailing list archives before posting.
I found previous reports involving 33-byte journal files filled with NUL bytes, where deleting the journal allowed recovery because .mbsyncstate still existed. My case appears different because: - .mbsyncstate is completely missing - .mbsyncstate.new is empty (0 bytes) - .mbsyncstate.journal is approximately 2.2 MB and contains valid ASCII records - inspecting the file around the reported offset (128959) does not show NUL bytes or an obvious truncation. Would it be useful if I attached the .mbsyncstate.journal file privately for analysis? *Best Regards* *Ali H. Hababi* +967 771228212 E: [email protected] Shoub Zone, Mazra'a, Sana'a, Yemen.
_______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
