percona-discussion team mailing list archive

[Vadim Tkachenko <vadim@xxxxxxxxxxx>]

Public bug reported:

 Version: '5.0.77-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
090520 18:47:32InnoDB: Assertion failure in thread 1185179968 in file ha_innodb.cc line 679
InnoDB: Failing assertion: cset == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
 InnoDB: about forcing recovery.
090520 18:47:32 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.


This  is  after  I  was  running  b13  on  this  box.  I  did  not use
extra_undo_segments in this case.

** Affects: percona-patches
     Importance: Critical
     Assignee: Yasufumi Kinoshita (yasufumi-kinoshita)
         Status: New

** Changed in: percona-patches
   Importance: Undecided => Critical

** Changed in: percona-patches
     Assignee: (unassigned) => Yasufumi Kinoshita (yasufumi-kinoshita)

-- 
Crash after downgrade from percona highperf
https://bugs.launchpad.net/bugs/378914
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona patches.

Status in Patches for MySQL by Percona: New

Bug description:
 Version: '5.0.77-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
090520 18:47:32InnoDB: Assertion failure in thread 1185179968 in file ha_innodb.cc line 679
InnoDB: Failing assertion: cset == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
 InnoDB: about forcing recovery.
090520 18:47:32 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.


This  is  after  I  was  running  b13  on  this  box.  I  did  not use
extra_undo_segments in this case.