<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-2022-JP">
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-html" lang="ja">
The MySQL database became corrupt after an unexpected power off. The
backups are impossible, and all I have to work with is the 39 GB
database. MySQL is always crashing in the same spot when I tried to
export with innodb_force_recovery with the values of 4 to 6. I then
tried using both the google innodb-tools and the innoinfo by Steve
Hardy. The innodb-tools doesn't really export much and the innodbinfo
utility gives me:<br>
<br>
<blockquote type="cite">Column found for non-existent table
000000000000008E .......�<br>
Segmentation fault <br>
</blockquote>
<br>
Below is the error that mysql crashes with. The information in this
database is pretty important. Any ideas?<br>
<br>
<br>
<blockquote type="cite">
<div class="text" style="font-family: monospace;">
<ol>
<li class="li1">
<div class="de1">Jun 15 11:02:54 ender mysqld[8364]: InnoDB:
space id 190 did not exist in memory. Retrying an open.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:54 ender mysqld[8364]: 100615
11:02:54 InnoDB: error: space object of table zarafa/singleinstances,
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:54 ender mysqld[8364]: InnoDB:
space id 194 did not exist in memory. Retrying an open.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:54 ender mysqld[8364]: 100615
11:02:54 InnoDB: error: space object of table zarafa/stores,
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:54 ender mysqld[8364]: InnoDB:
space id 180 did not exist in memory. Retrying an open.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:54 ender mysqld[8364]: 100615
11:02:54 InnoDB: error: space object of table zarafa/syncs,
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:54 ender mysqld[8364]: InnoDB:
space id 187 did not exist in memory. Retrying an open.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:54 ender mysqld[8364]: 100615
11:02:54 InnoDB: error: space object of table zarafa/usergroup_acl,
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:54 ender mysqld[8364]: InnoDB:
space id 181 did not exist in memory. Retrying an open.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:54 ender mysqld[8364]: 100615
11:02:54 InnoDB: error: space object of table zarafa/users,
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:54 ender mysqld[8364]: InnoDB:
space id 182 did not exist in memory. Retrying an open.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:54 ender mysqld[8364]: 100615
11:02:54 InnoDB: error: space object of table zarafa/versions,
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:54 ender mysqld[8364]: InnoDB:
space id 188 did not exist in memory. Retrying an open.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: 100615
11:02:55InnoDB: Assertion failure in thread 1077102928 in file
btr0pcur.c line 403
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: InnoDB:
Failing assertion: page_is_comp(next_page) == page_is_comp(page)
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: InnoDB: We
intentionally generate a memory trap.
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: InnoDB:
Submit a detailed bug report to <a class="moz-txt-link-freetext"
href="http://bugs.mysql.com">http://bugs.mysql.com</a>.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: InnoDB: If
you get repeated assertion failures or crashes, even
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: InnoDB:
immediately after the mysqld startup, there may be
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: InnoDB:
corruption in the InnoDB tablespace. Please refer to
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: InnoDB:
<a class="moz-txt-link-freetext"
href="http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html">http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html</a>
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: InnoDB:
about forcing recovery.
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: 100615
11:02:55 - mysqld got signal 11;
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: This could
be because you hit a bug. It is also possible that this binary
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: or one of
the libraries it was linked against is corrupt, improperly built,
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: or
misconfigured. This error can also be caused by malfunctioning
hardware.
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: We will try
our best to scrape up some info that will hopefully help diagnose
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: the problem,
but since we have already crashed, something is definitely wrong
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: and this may
fail.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]:
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]:
key_buffer_size=16777216
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]:
read_buffer_size=131072
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]:
max_used_connections=1
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]:
max_connections=500
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]:
threads_connected=1
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: It is
possible that mysqld could use up to
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]:
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 1104380 K
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: bytes of
memory
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: Hope that's
ok; if not, decrease some variables in the equation.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]:
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]:
thd=0x3214210
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: Attempting
backtrace. You can use the following information to find out
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: where mysqld
died. If you see no messages after this, something went
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: terribly
wrong...
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: Cannot
determine thread, fp=0x40333fd0, backtrace may not be correct.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: Stack range
sanity check OK, backtrace follows:
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: (nil)
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: New value of
fp=0x3214210 failed sanity check, terminating stack trace!
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: Please read
<a class="moz-txt-link-freetext"
href="http://dev.mysql.com/doc/mysql/en/using-stack-trace.html">http://dev.mysql.com/doc/mysql/en/using-stack-trace.html</a>
and follow
instructions on how to resolve the stack trace. Resolved
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: stack trace
is much more helpful in diagnosing the problem, so please do
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: resolve it
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: Trying to
get some variables.
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: Some
pointers may be invalid and cause the dump to abort...
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]:
thd->query at 0x324e370 = SELECT /*!40001 SQL_NO_CACHE */ * FROM
`changes`
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]:
thd->thread_id=7
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld[8364]: The manual
page at <a class="moz-txt-link-freetext"
href="http://www.mysql.com/doc/en/Crashing.html">http://www.mysql.com/doc/en/Crashing.html</a>
contains
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld[8364]: information
that should help you find out what is causing the crash.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender mysqld_safe[8762]: Number
of processes running now: 0
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:55 ender mysqld_safe[8764]:
restarted
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:55 ender kernel: [ 1872.933119]
audit(1276614175.648:8): type=1503 operation="capable"
name="sys_resource" pid=8766 profile="/usr/sbin/mysqld"
namespace="default"
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:56 ender mysqld[8767]: InnoDB: The
user has set SRV_FORCE_NO_LOG_REDO on
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:56 ender mysqld[8767]: InnoDB:
Skipping log redo
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:56 ender mysqld[8767]: InnoDB:
Database page corruption on disk or a failed
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:56 ender mysqld[8767]: InnoDB: file
read of page 4.
</div>
</li>
<li class="li1">
<div class="de1">Jun 15 11:02:56 ender mysqld[8767]: InnoDB: You
may have to recover from a backup.
</div>
</li>
<li class="li2">
<div class="de2">Jun 15 11:02:56 ender mysqld[8767]: 100615
11:02:56 InnoDB: Page dump in ascii and hex (16384 bytes):</div>
</li>
</ol>
</div>
</blockquote>
<br>
Thanks in advance.<br>
<br>
I really should have done backups differently.<br>
<pre class="moz-signature" cols="72">--
Mike A. Leonetti
As warm as green tea</pre>
</div>
</body>
</html>