On Fri, Dec 23 2016, Evgeniy Berdnikov wrote: >> Oswald is right, process completion (by exit() or interrupt by signal) >> can only truncate data, but can not corrupt. Only system crash can >> lead to data corruption. > > Oswald, I got the same Mbsync error without any crash and/or reboot, > after several monthes of normal run. Mbsync was invoked in a loop > "while sleep 30 ; do timeout 15s mbsync -a -V ; done". > Any concurrency with other mbsync process is completely ruled out. > > Error message was iether "mailformed journal entry" or "incomplete > journal entry", I do not remember exactly. The broken journal file > is 33 bytes length: > > % hd .mbsyncstate.journal > 00000000 32 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |2...............| > 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 00000021 > > After deletion of this file Mbsync continued to run as usual.
I'm glad mine is not the only case. I couldn't rule out other scenarios completely so far. ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
