http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-6538 Couchbase Server I experimented with building index on 6 cluster_run nodes and 9E6 simple docs. Everything went fine and results appeared right, but I&#39;m seeing <br/> <br/> <br/> [ns_server:debug,2012-09-05T21:31:14.218,<a href='mailto:n_5@10.17.21.241'>n_5@10.17.21.241</a>:compaction_daemon:compaction_daemon:schedule_next_compaction:1204]Finished compaction too soon. Next run will be in 30s <br/> [couchdb:error,2012-09-05T21:31:14.296,<a href='mailto:n_2@10.17.21.241'>n_2@10.17.21.241</a>:&lt;0.9681.0&gt;:couch_log:error:42]Set view `default`, replica group `_design/dev_t`, doc loader error <br/> error: {file_corruption,&lt;&lt;&quot;file corruption&quot;&gt;&gt;} <br/> stacktrace: [{couch_file,pread_iolist,2}, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{couch_db,open_doc_int,3}, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{couch_set_view_updater,load_doc,4}, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{couch_set_view_updater,&#39;-load_changes/7-fun-0-&#39;,6}, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{couch_btree,stream_kv_node2,8}, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{couch_btree,stream_kp_node,7}, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{couch_btree,fold,4}, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{couch_db,enum_docs_since,5}] <br/> <br/> [couchdb:error,2012-09-05T21:31:14.297,<a href='mailto:n_2@10.17.21.241'>n_2@10.17.21.241</a>:&lt;0.6715.0&gt;:couch_log:error:42]Set view `default`, replica group `_design/dev_t`, received error from updater: {file_corruption, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;&lt;&quot;file corruption&quot;&gt;&gt;} <br/> [couchdb:info,2012-09-05T21:31:17.856,<a href='mailto:n_2@10.17.21.241'>n_2@10.17.21.241</a>:&lt;0.6715.0&gt;:couch_log:info:39]Starting updater for set view `default`, replica group `_design/dev_t` <br/> [couchdb:info,2012-09-05T21:31:17.856,<a href='mailto:n_2@10.17.21.241'>n_2@10.17.21.241</a>:&lt;0.9753.0&gt;:couch_log:info:39]Updater for set view `default`, replica group `_design/dev_t` started <br/> <br/> <br/> in logs. Will attach logs from this box. MB-6538

In rare cases CRC codes dont match when reading data from couch file

Bug Blocker Resolved Incomplete Public Aaron Miller Aleksey Kondratenko 2.0-beta-release-notes Wed, 5 Sep 2012 23:33:03 -0500 Wed, 24 Oct 2012 12:13:24 -0500 Wed, 24 Oct 2012 12:13:24 -0500 2.0 storage-engine 0 2 Which build? ohh. cluster_run This happens when reading from a database file, not from an index file. corrupted files attached in the corrupted doc in 252.couch it looks like the file got stomped on by one byte. Both docs have the same CRC, and should have the same data, but this byte got messed up somehow. see attached screenshot other file (253.couch.1) I don&#39;t understand the name change here. The files in question were never compacted. Added to beta release notes: In rare cases codes used to test for data corruption (CRC, checksum) codes do not match when reading data from couch <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;file. Aliaksey, <br/> <br/> did you use RAM disk for persistence when running this test ? No. Don&#39;t understand why this would matter. _Any_ (well except for direct io) write to filesystem is write to kernel&#39;s page cache first. <br/> We think this was a regression, possibly a dangling pointer, in the ep-engine that has since been fixed. Please reopen if there is another instance of the recently. got this again vbucket in question was in bucket other which was populated by incoming xdcr attaching diags from node having that badness Single byte error again. Sorry folks, found that my box actually has bad RAM. Date of First Response Wed, 5 Sep 2012 23:34:37 -0500 Rank 4104 Time In Status