hello oswald, thank you for your response.
On Sat, Aug 16, 2014 at 11:33:29AM +0200, Oswald Buddenhagen wrote:
> > the file
> > ~/.mbsync/:poseidonmailbox:mailinglists!intern_:local:mailinglists.intern
> > is empty.
> >
> it would be interesting to know what other variations of the file name
> you have there. if you have it with a .new suffix and it looks
> reasonable, you may get lucky by just renaming it over the old one
there is exactly one .new file in that folder
(~/.mbsync/:poseidonmailbox:mailinglists!debian-newmaint_:local:mailinglists!debian-newmaint.new)
-- it is empty, does not belong to any of the affected folders, and
seems to sync perfectly fine.
> the presence and contents (just the tail) of a .journal variant would
> also be interesting for diagnostic reasons.
there is a .journal file for the newmaint list folder ("2\n| 1305464539
1391093930\n" and a bunch of + * # lines, later > lines; looks normal).
for the affected folder 'mailinglists/students-217' (the first in the
sequence of affected folders), there is a .journal file; it only
contains "2\n".
> what did you configure FSync to?
i didn't touch that setting, so it should been 'yes'.
> mbsync unfortunately has no way to recover from a lost sync state (which
> is eqivalent with bootstrapping pre-existing stores - say, a migration
> from offlineimap, which comes up here from time to time, last time just
> days ago). such a recovery would be heuristical, so there are cases
> where it would fail. and somebody needs to implement it.
i'll resist the temptation of heuristics and do a clean one-way sync
later; for the time being, i can leave the state around and just not
read the affected folders.
is there anything else i can scrape together that might help finding out
what caused the current state?
> as long as you have no unpropagated local messages, deleting the local
> folders (and remnants of the sync state) and starting from scratch is
> the most reasonable recovery.
i know of sync state being tracked in the .uidvalidity files in the
maildir folders themselves, and of the files in ~/.mbsync. any other
state i need to take care of?
best regards
chrysn
--
To use raw power is to make yourself infinitely vulnerable to greater powers.
-- Bene Gesserit axiom
signature.asc
Description: Digital signature
------------------------------------------------------------------------------
_______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
