MySQL Bugs: #65276: Mysql engine failure on innodb table open fail

Bug #65276	Mysql engine failure on innodb table open fail
Submitted:	10 May 2012 7:59	Modified:	10 Jun 2012 12:06
Reporter:	carlo tollo	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.5.23	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Here you have our report :

120509 18:08:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name .\sa2367166\po131.ibd
InnoDB: File operation call: 'open'.
120509 18:08:19  InnoDB: Assertion failure in thread 2480 in file fil0fil.c line 832
InnoDB: Failing assertion: ret
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.
InnoDB: Thread 1524 stopped in file os0sync.c line 781
InnoDB: Thread 3760 stopped in file os0sync.c line 474
InnoDB: Thread 3452 stopped in file sync0arr.c line 359

How to repeat:
the error is random, we've got it three times this week.

Are you tried the instructions of http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html ?. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".