Extra-info descriptors have corrupt {write,read}-history lines

While parsing extra-info descriptors for the dir bytes analysis, I found that some of them have weird write-history or read-history lines with obviously wrong dates. I wonder what leads to these false reports and if there are more errors like this in extra-info descriptors.

Here are some examples:

published 2010-09-03 08:21:00
write-history 2002-01-01 00:47:32 (900 s) 0,109568,44032,189440,219136,
92160,190464,354304,126976
read-history 2002-01-01 00:47:32 (900 s) 816128,1042432,163840,180224,
2770944,221184,133120,359424,770048

published 2010-06-08 19:20:14
write-history 2003-01-01 02:20:36 (900 s) 8192,26624,18432,49152,169984
read-history 2003-01-01 02:20:36 (900 s) 147456,154624,13312,23552,2411520

published 2010-08-17 17:14:51
write-history 2003-01-01 03:16:39 (900 s) 3454976
read-history 2010-08-17 04:16:39 (900 s)

published 2010-08-31 12:12:21
write-history 2002-01-01 03:06:31 (900 s) 117760,69632,59392,52224,61440,
871424,3474432,3022848,4219904,2000896,160768,138240,138240,175104,131072,
47104,59392,33792,37888,87040
read-history 2002-01-01 03:06:31 (900 s) 1923072,52224,194560,35840,
1046528,906240,3657728,3198976,5303296,2452480,338944,423936,1155072,
308224,119808,193536,1045504,91136,191488,104448

published 2010-08-31 12:12:28
write-history 2002-01-01 03:06:31 (900 s) 117760,69632,59392,52224,61440,
871424,3474432,3022848,4219904,2000896,160768,138240,138240,175104,131072,
47104,59392,33792,37888,87040
read-history 2010-08-31 12:06:31 (900 s) 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0

published 2010-05-28 21:30:25
write-history 2010-05-28 21:15:26 (900 s) 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0
read-history 1970-01-02 07:45:26 (900 s) 1245184,447488,1458176,1916928,
324608,479232,133120,272384,1698816,791552,573440,381952,352256,667648,
451584,861184,515072,902144,301056,5548032,14390272,11052032,395264,
372736,250880,560128,202752,199680,1078272,915456,2571264,227328,194560,
602112,189440,325632,194560,450560,320512,180224,263168,488448,167936,
172032,135168,506880,175104,205824,23552,401408,21504,21504,180224,274432,
18432,139264,15360,399360,13312,143360,20480,405504,16384,143360,16384,
398336,11264,142336,15360,270336,15360,143360,15360,398336,15360,14336,
20480,407552,18432,147456,13312,414720,13312,144384,10240,406528,3072,
135168,8192,270336,4096,7168,5120,404480,7168,5120

Any idea what causes this problem? I didn't find an obvious pattern in these examples. Is it just memory corruption on the relays?