<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Mon May 20 04:24:54 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.couchbase.com/issues/si/jira.issueviews:issue-xml/MB-5095/MB-5095.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[MB-5095] Failures on Backing up of Data with Large WAL size on 1.8.1 throws error : Database disk image is malformed</title>
                <link>http://www.couchbase.com/issues/browse/MB-5095</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>Backup fails for files w/ large size WAL[ 5M plus]. Backup is successful for smaller WAL sizes [default :1000].&lt;br/&gt;
&lt;br/&gt;
Steps to Reproduce this issue&lt;br/&gt;
------------------------------------------------------&lt;br/&gt;
&lt;br/&gt;
Load 1M of data : [/opt/couchbase/bin/memcachetest -h localhost:11211 -i 1000000 -M 1024 -K cb_2 -l ]&lt;br/&gt;
Run a backup of the data [ while database is online] : sudo -su couchbase /opt/couchbase/bin/cbbackup  /opt/couchbase/var/lib/couchbase/data/default-data/default /tmp/rev7&lt;br/&gt;
&lt;br/&gt;
Errors&lt;br/&gt;
--------------------------------------------------------&lt;br/&gt;
..&lt;br/&gt;
Backup of default done, check integrity now&lt;br/&gt;
ok&lt;br/&gt;
Vacuum of default done&lt;br/&gt;
Backup of default-0.mb done, check integrity now&lt;br/&gt;
*** in database main ***&lt;br/&gt;
On tree page 395901 cell 3: 2nd reference to page 395903&lt;br/&gt;
On tree page 426067 cell 0: 2nd reference to page 410862&lt;br/&gt;
On tree page 426067 cell 1: 2nd reference to page 410863&lt;br/&gt;
.&lt;br/&gt;
.&lt;br/&gt;
.&lt;br/&gt;
.&lt;br/&gt;
&lt;br/&gt;
On tree page 461483 cell 2: 2nd reference to page 462480&lt;br/&gt;
On tree page 467250 cell 1: 2nd reference to page 440802&lt;br/&gt;
On tree page 472512 cell 1: 2nd reference to page 471560&lt;br/&gt;
On tree page 358585 cell 1: 2nd reference to page 358586&lt;br/&gt;
On tree page 474942 cell 1: 2nd reference to page 473623&lt;br/&gt;
Page 491172: btreeInitPage() returns error code 11&lt;br/&gt;
On tree page 485795 cell 89: Child page depth differs&lt;br/&gt;
Page 491173: btreeInitPage() returns error code 11&lt;br/&gt;
Page 491175: btreeInitPage() returns error code 11&lt;br/&gt;
On tree page 336498 cell 0: 2nd reference to page 336497&lt;br/&gt;
On tree page 385778 cell 2: 2nd reference to page 385777&lt;br/&gt;
On tree page 394903 cell 1: 2nd reference to page 394901&lt;br/&gt;
On tree page 427473 cell 1: 2nd reference to page 427474&lt;br/&gt;
On tree page 436046 cell 0: 2nd reference to page 436045&lt;br/&gt;
On tree page 437909 cell 0: 2nd reference to page 437907&lt;br/&gt;
On tree page 444827 cell 1: 2nd reference to page 444046&lt;br/&gt;
On tree page 467244 cell 0: 2nd reference to page 471558&lt;br/&gt;
On tree page 483494 cell 0: 2nd reference to page 469621&lt;br/&gt;
On tree page 376439 cell 1: 2nd reference to page 376440&lt;br/&gt;
On tree page 376453 cell 1: 2nd reference to page 376412&lt;br/&gt;
On tree page 399713 cell 2: 2nd reference to page 399714&lt;br/&gt;
On tree page 411158 cell 1: 2nd reference to page 412526&lt;br/&gt;
On tree page 426543 cell 0: 2nd reference to page 362805&lt;br/&gt;
Page 491168: btreeInitPage() returns error code 11&lt;br/&gt;
On tree page 482558 cell 86: Child page depth differs&lt;br/&gt;
Page 491169: btreeInitPage() returns error code 11&lt;br/&gt;
Page 491170: btreeInitPage() returns error code 11&lt;br/&gt;
Page 491171: btreeInitPage() returns error code 11&lt;br/&gt;
On tree page 385413 cell 1: 2nd reference to page 385411&lt;br/&gt;
On tree page 407221 cell 1: 2nd reference to page 407222&lt;br/&gt;
On tree page 416240 cell 1: 2nd reference to page 416241&lt;br/&gt;
On tree page 426539 cell 1: 2nd reference to page 427355&lt;br/&gt;
On tree page 430171 cell 2: 2nd reference to page 429186&lt;br/&gt;
On tree page 433173 cell 0: 2nd reference to page 433172&lt;br/&gt;
On tree page 434095 cell 1: 2nd reference to page 434096&lt;br/&gt;
On tree page 439678 cell 0: 2nd reference to page 439677&lt;br/&gt;
On tree page 479441 cell 1: 2nd reference to page 479442&lt;br/&gt;
Page 491162: btreeInitPage() returns error code 11&lt;br/&gt;
On tree page 487719 cell 79: Child page depth differs&lt;br/&gt;
Page 491163: btreeInitPage() returns error code 11&lt;br/&gt;
Page 491166: btreeInitPage() returns error code 11&lt;br/&gt;
On tree page 376307 cell 1: 2nd reference to page 376308&lt;br/&gt;
On tree page 385403 cell 1: 2nd reference to page 388156&lt;br/&gt;
On tree page 428240 cell 1: 2nd reference to page 428241&lt;br/&gt;
On tree page 430165 cell 3: 2nd reference to page 430166&lt;br/&gt;
Error: database disk image is malformed&lt;br/&gt;
Vacuum of default-3.mb done&lt;br/&gt;
</description>
                <environment>Operating System : Ubuntu Single Node&lt;br/&gt;
Branch : 1.8.1-753&lt;br/&gt;
</environment>
            <key id="16642">MB-5095</key>
            <summary>Failures on Backing up of Data with Large WAL size on 1.8.1 throws error : Database disk image is malformed</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/major.png">Major</priority>
                    <status id="6" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/closed.png">Closed</status>
                    <resolution id="2">Won&apos;t Fix</resolution>
                    <security id="10011">Public</security>
                        <assignee username="steve">Steve Yen</assignee>
                                <reporter username="ketaki">Ketaki Gangal</reporter>
                        <labels>
                    </labels>
                <created>Mon, 16 Apr 2012 21:07:44 -0500</created>
                <updated>Thu, 10 Jan 2013 01:14:18 -0600</updated>
                    <resolved>Wed, 3 Oct 2012 16:45:10 -0500</resolved>
                            <version>1.8.1</version>
                                <fixVersion>2.0</fixVersion>
                                <component>tools</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="30074" author="dipti" created="Thu, 14 Jun 2012 19:55:58 -0500"  >is there a workaround? </comment>
                    <comment id="30076" author="karan" created="Thu, 14 Jun 2012 20:04:25 -0500"  >Ohh.. Sorry I posted the wrong comment.. </comment>
                    <comment id="30077" author="karan" created="Thu, 14 Jun 2012 20:05:12 -0500"  >@Steve: Not sure if you have taken a look at this?.. This bug was wrongly tagged and did not show up in the filter. </comment>
                    <comment id="30134" author="steve" created="Fri, 15 Jun 2012 13:22:53 -0500"  >Still trying to reproduce.  Running single node centos 1.8.1-910, with 3M items created via a concurrent mix of memcachetest and mcsoda...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;/opt/couchbase/bin/memcachetest -h localhost:11211 -i 1000000 -M 1024 -K cb_0 -l -P 95&lt;br/&gt;
&amp;nbsp;&amp;nbsp;./pytests/performance/mcsoda.py &lt;a href=&quot;membase://HOST:8091&quot;&gt;membase://HOST:8091&lt;/a&gt; max-items=200000 ratio-sets=1.0 vbuckets=1024 doc-gen=0&lt;br/&gt;
&lt;br/&gt;
While the client load tools were running, backup took forever...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;/opt/couchbase/bin/cbbackup /opt/couchbase/var/lib/couchbase/data/default-data/default /tmp/backup0&lt;br/&gt;
&lt;br/&gt;
After stopping the client load tools, the backup eventually finished.&lt;br/&gt;
&lt;br/&gt;
WAL sizes were &amp;gt;1MB, but no malformed issues so far...&lt;br/&gt;
&lt;br/&gt;
# ls -al /opt/couchbase/var/lib/couchbase/data/default-data/total 1443244&lt;br/&gt;
drwxr-xr-x 2 couchbase couchbase      4096 2012-06-15 05:11 .&lt;br/&gt;
drwxr-xr-x 3 couchbase couchbase      4096 2012-06-14 08:48 ..&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase     52224 2012-06-15 04:57 default&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase 489541632 2012-06-15 05:09 default-0.mb&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase     32768 2012-06-15 05:08 default-0.mb-shm&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase   2618984 2012-06-15 05:09 default-0.mb-wal&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase 326151168 2012-06-15 05:09 default-1.mb&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase     32768 2012-06-15 05:08 default-1.mb-shm&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase   1618144 2012-06-15 05:09 default-1.mb-wal&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase 327179264 2012-06-15 05:09 default-2.mb&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase     32768 2012-06-15 05:08 default-2.mb-shm&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase   1473520 2012-06-15 05:09 default-2.mb-wal&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase 326189056 2012-06-15 05:09 default-3.mb&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase     32768 2012-06-15 05:08 default-3.mb-shm&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase   1768008 2012-06-15 05:09 default-3.mb-wal&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase     32768 2012-06-15 05:11 default-shm&lt;br/&gt;
-rw-r--r-- 1 couchbase couchbase   1084712 2012-06-15 05:11 default-wal&lt;br/&gt;
&lt;br/&gt;
</comment>
                    <comment id="30144" author="steve" created="Fri, 15 Jun 2012 14:53:46 -0500"  >When I run memcachetest/mcsoda at full speed, then cbbackup appears to not make any progress.  It&amp;#39;s likely that cbbackup is unable to acquire file locks, since ep-engine has them and isn&amp;#39;t letting go.&lt;br/&gt;
&lt;br/&gt;
When I run client-load-tools at a slower ops/second (max-ops-per-sec), then cbbackup does finish...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;./pytests/performance/mcsoda.py &lt;a href=&quot;membase://10.3.121.192:8091&quot;&gt;membase://10.3.121.192:8091&lt;/a&gt; max-items=200000 ratio-sets=0.1 vbuckets=1024 doc-gen=0 cur-items=200000 max-ops-per-sec=10&lt;br/&gt;
&lt;br/&gt;
In either case, I haven&amp;#39;t reproduced the &amp;quot;image is malformed&amp;quot; issue yet.</comment>
                    <comment id="30812" author="dipti" created="Thu, 21 Jun 2012 02:33:51 -0500"  >is this using old cbbackup or tap backup? is this still current sprint / P0 ? </comment>
                    <comment id="30833" author="farshid" created="Thu, 21 Jun 2012 11:15:15 -0500"  >wait until wal file size is less than 10 MB before running cbbackup</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Thu, 14 Jun 2012 19:55:58 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>5471</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                                                                                                        <customfield id="customfield_10181" key="com.atlassian.jira.ext.charting:timeinstatus">
                <customfieldname>Time In Status</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                </customfields>
    </item>
</channel>
</rss>