Snappy will be adding checksums when it compresses and verifying them when it decompresses (right?). So all we have here is a corruption detection mechanism firing when it sees corruption. It tells us nothing about the cause.
B. On 18 April 2013 14:39, Jan Lehnardt <[email protected]> wrote: > Sorry, I jumped the gun with the original mail because I was on the go > and thought dev@ should know asap. > > Maybe this isn’t snappy related at all either. > > Jan > -- > > On Apr 18, 2013, at 15:32 , Robert Newson <[email protected]> wrote: > >> "Bob N looked at this and found this in the logs" >> >> This is not quite right. I took the file from the site and loaded it >> into my local dev couch. I called _all_docs and that's what my log >> gave. >> >> I suggest this thread ends now and we continue all this on the ticket >> opened by the original reporter. >> >> B. >> >> >> On 18 April 2013 14:16, Benoit Chesneau <[email protected]> wrote: >>> On Thu, Apr 18, 2013 at 2:38 PM, Jan Lehnardt <[email protected]> wrote: >>>> It's linked in the post. >>>> >>>> Cheers >>>> Jan >>>> -- >>>> >>> >>> Last mail linked it as well. >
