Comment 2 for bug 1193350

2013-05-29 22:12:52 16627 [Note] /ssd/Percona-Server-5.6.11-alpha60.3-363.Linux.x86_64/bin/mysqld: ready for connections.
Version: '5.6.11-alpha60.3-log' socket: '/ssd/244301/current1_7/tmp/master.sock' port: 13120 Percona Server with XtraDB (GPL), Release alpha60.3, Revision 363
2013-05-29 22:15:20 16627 [Warning] InnoDB: changed page bitmap file './ib_modified_log_1_0.xdb' does not contain a complete run at the end.

2013-05-29 22:15:35 16627 [Warning] InnoDB: error opening the changed page bitmap './ib_modified_log_1_0.xdb'

2013-05-29 22:16:37 16627 [ERROR] InnoDB: Tried to read 4096 bytes at offset 0. Was only able to read 0.
2013-05-29 22:16:37 7f712bfbe700 InnoDB: Operating system error number 21 in a file operation.
InnoDB: Error number 21 means 'Is a directory'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Fatal error: cannot read from file. OS error number 21.
2013-05-29 22:16:37 7f712bfbe700 InnoDB: Assertion failure in thread 140124045960960 in file os0file.cc line 2821
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
19:16:37 UTC - mysqld got signal 6 ;