[Bug 1456167] Re: InnoDB crashes with assertion failure in file fut0lst.ic line 83 (addr.page == FIL_NULL || addr.boffset = FIL_PAGE_DATA)

[Expired for mysql-5.5 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mysql-5.5 (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1456167] Re: InnoDB crashes with assertion failure in file fut0lst.ic line 83 (addr.page == FIL_NULL || addr.boffset = FIL_PAGE_DATA)

[Expired for mysql-5.5 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mysql-5.5 (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu.

[Bug 1456167] Re: InnoDB crashes with assertion failure in file fut0lst.ic line 83 (addr.page == FIL_NULL || addr.boffset = FIL_PAGE_DATA)

Thanks Morgan. Marking as Incomplete for now, as local corruption unrelated to a MySQL bug sounds like an equally valid possibility. If new information is found that suggests that this is a bug, then this bug can be changed back to New. Otherwise we can assume it was local corruption. ** Changed

[Bug 1456167] Re: InnoDB crashes with assertion failure in file fut0lst.ic line 83 (addr.page == FIL_NULL || addr.boffset = FIL_PAGE_DATA)

Two cents from me: This looks like an InnoDB assertion (a deliberate crash because the data file is in an inconsistent state, and proceeding is considered unsafe). Assertions can either be the result of an unsafe shutdown with non-durable settings (or hardware) or bugs in MySQL code. -- You