couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <paul.joseph.da...@gmail.com>
Subject Re: Corrupted database example file
Date Thu, 18 Apr 2013 16:47:44 GMT
Investigating this locally. Reproduced in that it fails locally. I've
narrowed down the exact binary that's failing snappy decompression
fairly easily. So far my debugging is showing that snappy is trying to
decode this binary into a format that ends up exceeding the
decompressed size that it thought it was going to need which suggests
some sort of corruption within this binary. Still trying to figure out
where the exact bit of corruption is.

In case anyone is interested, here's the binary:

<<148,8,232,131,104,2,100,0,7,107,112,95,110,111,100,101,108,0,0,0,
 25,104,2,109,0,0,0,11,50,122,119,82,121,49,90,66,49,118,107,104,3,
 98,0,8,232,117,104,3,97,13,97,0,98,0,0,8,98,98,0,0,3,36,13,41,44,
 51,49,50,81,113,48,114,81,56,84,78,104,1,41,20,235,153,104,3,97,
 12,5,41,24,7,54,98,0,0,3,28,17,41,36,51,50,86,110,48,77,121,55,75,
 82,5,41,4,238,181,21,41,4,6,158,1,41,0,1,29,41,32,56,99,70,48,98,
 111,55,75,81,5,41,4,241,182,25,41,20,137,98,0,0,2,221,21,41,32,
 114,71,108,48,53,111,55,109,87,5,41,4,244,147,21,164,4,7,9,1,41,0,
 211,17,41,36,52,114,69,85,48,50,49,55,67,109,5,41,4,247,102,25,41,
 0,25,1,123,0,5,17,41,36,53,68,108,48,48,115,120,55,67,100,5,41,4,
 250,107,25,41,0,18,1,82,0,240,21,41,20,101,89,79,49,78,113,17,82,
 20,253,91,104,3,97,14,9,246,5,164,0,244,21,41,20,104,116,65,49,98,
 90,13,82,8,9,0,79,21,82,4,6,254,1,82,0,237,17,41,24,54,51,110,104,
 50,80,100,13,82,8,9,3,60,21,41,4,7,30,1,164,0,12,21,41,20,78,120,
 81,50,109,52,17,82,4,6,72,21,41,9,82,0,222,17,41,36,55,56,53,110,
 48,68,107,53,102,76,1,205,8,9,9,38,57,72,0,143,1,123,0,241,17,41,
 36,56,69,53,52,48,107,55,54,70,52,5,41,4,12,23,21,82,4,7,27,1,41,
 0,224,25,41,28,115,117,48,51,79,55,76,102,5,41,20,14,247,104,3,97,
 15,9,246,0,235,1,41,0,185,21,41,32,89,67,57,48,55,119,48,103,68,5,
 41,4,17,176,25,82,0,15,1,41,0,208,21,41,32,114,106,117,48,90,97,
 48,103,66,5,41,4,20,128,25,164,0,139,1,41,0,218,17,41,32,57,97,73,
 90,48,52,52,54,97,69,62,8,9,23,90,25,82,0,12,1,41,21,82,32,65,104,
 121,78,49,98,70,54,98,37,236,8,9,26,42,25,41,0,21,1,41,53,154,64,
 66,48,117,98,48,56,70,55,50,73,104,3,98,0,9,29,30,25,123,0,153,1,
 41,0,240,17,123,32,66,51,76,51,48,76,90,55,51,9,82,4,32,14,25,82,
 0,5,1,41,0,210,21,41,20,76,101,121,48,115,50,17,82,4,34,224,25,82,
 37,113,0,215,17,41,36,67,122,87,103,48,84,117,52,107,119,5,123,8,
 37,183,104,85,62,0,115,50,82,0,36,69,77,55,104,48,76,108,52,67,
 105,5,41,4,40,137,25,82,5,164,0,245,17,82,32,69,78,68,98,48,51,81,
 48,121,41,72,4,43,126,57,154,0,233,1,82,53,154,36,70,110,54,108,
 48,52,71,54,79,90,5,82,4,46,55,25,123,24,145,98,0,0,2,245,106>>

On Thu, Apr 18, 2013 at 9:03 AM, Benoit Chesneau <bchesneau@gmail.com> wrote:
> On Thu, Apr 18, 2013 at 3:05 PM, Robert Newson <rnewson@apache.org> wrote:
>> Hi Victor,
>>
>> Thanks for the report and for capturing a .couch file in this state. I
>> have reproduced the error locally with 1.2.0.
>>
>> Can you tell me anything about what was happening before this
>> happened? Did you ever run out of disk space or have other disk
>> issues? What operating system? what version of erlang? which
>> filesystem? which mount options?
>>
> also what was the load at that point (CPU and such). Do you have any
> other error in logs before that?
>
> - benoit

Mime
View raw message