On Wed, Oct 19, 2005 at 08:03:08AM -0500, John Goerzen wrote: > On Tue, Oct 18, 2005 at 03:44:42PM +0100, Paul Brossier wrote: > > Package: offlineimap > > Version: 4.0.11 > > Severity: important > > > > offlineimap now synchronises the first 80 folders without problems, but > > crashes > > on the 81st one. If i move away that folder, the error occurs on the next > > one. > > Neither have been modified in the last month, no idea how i came to this > > point. > > Running with -1 doesn't help. > > This particular error could only occur when some local status file gets > corrupted. > > If you look in ~/.offlineimap/Account-(whatever)/LocalStatus, you should > see a file for each folder that is being synchronized. In there, each > file should have its first line be: > > OFFLINEIMAP LocalStatus CACHE DATA - DO NOT MODIFY - FORMAT 1 > > The error you are getting indicates that the folder in question doesn't > have that in its first line. > > I've never heard of this happening before, and frankly it would be very > difficult to duplicate it, as the code that does this looks like: > > self.savelock.acquire() > try: > file = open(self.filename + ".tmp", "wt") > file.write(magicline + "\n") > > So I'm curious about what actually is in that file, and the file for > apparently another folder. I can't think of much aside from a full disk > that could cause this. > >
arg. using xfs? all the LocalStatus files but the first 80 ones were full of 0. deleting them fixed the problem. i can't find a bug on linux-2.6 about empty files with xfs, but it is a known issue, so i guess this bug can be closed. cheers, piem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
