Thanks for your help.
> ----- Original Message ----- > From: Oswald Buddenhagen > Sent: 06/23/13 01:55 AM > To: [email protected] > Subject: Re: .mbsyncstate files corrupted: all zeros > > On Sat, Jun 22, 2013 at 02:20:18PM -0400, [email protected] wrote: > > Looking at the .mbsyncstate files showed they were all filled with Nulls. > > > this is typically what a file system like xfs would do after a crash. I don't know enough about linux file systems to know if it's significant, but my system uses ext4. > > > I have been using the git version of mbsync for a couple weeks (since > > June 13). > > > hmpf. the above should not happen then - see the FSync option. I hadn't noticed the Fsync option. I'll add it to my config files. > > anyway, there is no plausible way how mbsync itself could write a state > file of all zeros (it's a text file written line wise). > > you should check your kernel log for anything unusual. Nothing unusual in the kernel log. I do run linux in a VMWare client on a laptop, though. So perhaps there is something about that which would cause problems. (just speculating) > > > Is there any way to recover the .mbsyncstate files, short of > > downloading everything from all the IMAP servers again? > > > nope. Bummer. But at least the messages haven't been lost. > > some nitpicks re your config: Thanks for the tips on streamlining my config. > > > CertificateFile ... > > CertificateFile ... > > CertificateFile ... > > > only the last instance is effective. > > > Inbox ~/path/to/Acct1/mail/Inbox > > > you don't actually need that, as you don't refer to INBOX (yes, all > uppercase) anywhere: > > > Master :Acct1-imap:Inbox > > > the server will likely treat that as the INBOX ... > > > Slave :Acct1-local:Inbox > > > ... but mbsync won't. > > none of this actually matters, you just could streamline a bit. > > regards ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
