[PATCH] More detailed error output on corrupt UID mapping files

Sebastian Spaeth Sebastian at SSpaeth.de
Tue May 3 18:03:39 BST 2011

On Tue, 3 May 2011 08:07:43 -0700 (PDT), chris coleman wrote:

> 1) I ran 6.3.3.  Same results:

No, actually we got new information... It *is* corrupt data. 

>   File "/root/nicolas33-offlineimap-v633/offlineimap/folder/LocalStatus.py", line 82, in cachemessagelist
>     uid = long(uid)
> ValueError: null byte in argument for long()

Here you go ^^^  I thought this is in response to some IMAP reply. The
above full traceback (that we only got in 6.3.3) makes it clear that
this happens while reading the LocalStatus file and it is *just* a
corrupt data file.

I'll reply to this email with a patch based on 6.3.3 which is similar to
the previous patch and which will output the exact filename and line
that are corrupt.

I am a bit concerned that you might have some unreliable disks or other
hardware errors. It is weird to see so many corrupt files because they
really shouldn't occur. We first write to a temporary file and move that
to the final place when it is finished, so I am somewhat concerned that
you see these corruptions.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/offlineimap-project/attachments/20110503/7b4486b6/attachment-0001.sig>

More information about the OfflineIMAP-project mailing list