Comment 3 for bug 1086700

Error log:

121204 5:04:23 [Note] /data/ssd/qa/Percona-Server-5.5.28-rel29.1-359.Linux.x86_64/bin/mysqld: ready for connections.
Version: '5.5.28-rel29.1-log' socket: '/data/ssd/qa/104/current1_6/tmp/master.sock' port: 13100 Percona Server with XtraDB (GPL), Release rel29.1, Revision 359
InnoDB: Warning: hash index ref_count (2) is not zero after fil_discard_tablespace().
index: "PRIMARY" table: "test/table500_innodb_dynamic_int_autoinc"
[... above message repeated 3x ...]
InnoDB: Warning: hash index ref_count (2) is not zero after fil_discard_tablespace().
index: "c34" table: "test/table500_innodb_dynamic"
InnoDB: Warning: hash index ref_count (2) is not zero after fil_discard_tablespace().
index: "c34" table: "test/table500_innodb_dynamic"
121204 5:06:23 InnoDB: Error: trying to access tablespace 148 page no. 49,
InnoDB: but the tablespace does not exist or is just being dropped.
[... above message repeated many times ...]
121204 5:06:23 InnoDB: Error: trying to access tablespace 148 page no. 49,
InnoDB: but the tablespace does not exist or is just being dropped.
InnoDB: Error: Unable to read tablespace 148 page no 49 into the buffer pool after 100 attempts
InnoDB: The most probable cause of this error may be that the table has been corrupted.
InnoDB: You can try to fix this problem by using innodb_force_recovery.
InnoDB: Please see reference manual for more details.
InnoDB: Aborting...
121204 5:06:23 InnoDB: Assertion failure in thread 1085233472 in file buf0buf.c line 2608
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:06:23 UTC - mysqld got signal 6 ;