Bug #45297 Crash during recovery due to pread reading beyond EOF
Submitted: 3 Jun 2009 10:57 Modified: 26 May 2010 17:47
Reporter: Olav Sandstå Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server: Falcon storage engine Severity:S2 (Serious)
Version:6.0.12-alpha OS:Linux
Assigned to: Olav Sandstå CPU Architecture:Any
Triage: Triaged: D1 (Critical)

[3 Jun 2009 10:57] Olav Sandstå
When running falcon_many_indexes: During recovery stage 3 Falcon crashes with the following error message:

[Falcon] Error: pread on file /export/home/.clip./vardirs/master-data_recovery/falcon_user.fts from  page 16858751 (offset 69053444096) returned 0 bytes instead of 4096 (possible read behind EOF)

This is likely an attempt to read beyond the end of the file.

The call stack looks like:

/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Error::debugBreak()+0x12) [0x8569fa8]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Error::error(char const*, ...)+0x7a) [0x856a024]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(IO::readPage(Bdb*)+0x1ec) [0x85d56b2]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Cache::fetchPage(Dbb*, int, PageType, LockType)+0x36b) [0x8656ec7]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Dbb::fetchPage(int, PageType, LockType)+0x48) [0x85c7ac8]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(PageInventoryPage::isPageInUse(Dbb*, int)+0x7b) [0x85f8d6f]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Cache::fetchPage(Dbb*, int, PageType, LockType)+0xe4) [0x8656c40]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Dbb::fetchPage(int, PageType, LockType)+0x48) [0x85c7ac8]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(DataPage::deleteOverflowPages(Dbb*, int, unsigned int)+0x8c) [0x865a8c0]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(DataPage::updateRecord(Section*, int, Stream*, unsigned int, bool)+0x85) [0x865b105]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Section::updateRecord(int, Stream*, unsigned int, bool)+0x3eb) [0x8625b01]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Dbb::updateRecord(int, int, Stream*, unsigned int, bool)+0x49) [0x85ca001]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(SRLUpdateRecords::redo()+0x2a8) [0x861d610]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(SerialLog::recover()+0xd79) [0x862dee9]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Database::openDatabase(char const*)+0x341) [0x85c037f]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Connection::getDatabase(char const*, char const*, Threads*)+0x149) [0x85b327d]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(Connection::openDatabase(char const*, char const*, char const*, char const*, char const*, Threads*)+0x198) [0x85b479a]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(StorageDatabase::getOpenConnection()+0x86) [0x857850c]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(StorageHandler::initialize()+0x9f) [0x857abf5]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(StorageInterface::falcon_init(void*)+0x256) [0x85613d4]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0xa3) [0x840cadf]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld [0x84c479e]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(plugin_init(int*, char**, int)+0x695) [0x84c5d05]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld [0x82c4f31]
/export/home/pb2/test/sb_1-548791-1243518052.79/mysql-6.0.12-alpha-linux-i686-test/libexec/mysqld(main+0x1de) [0x82c5eea]
/lib/libc.so.6(__libc_start_main+0xdc) [0x736dec]

How to repeat:
Seen once after running falcon_many_indexes.
[3 Jun 2009 11:03] Olav Sandstå
Parts of the call stack is similar to the call stack in Bug#44744. Setting it to Analyzing while checking out if this is caused by the same problem as in Bug#44744.
[8 Jun 2009 13:40] Olav Sandstå
Having re-run the recovery and looked at the core file I find that this crash is very similar to Bug#44744.

What happens is that:

1. A call to DataPage::updateRecord() is done with a lineNumber that is equal to maxLine (same as in Bug#44744).

2. When checking the value of the LineIndex entry we find that this represent an overflow page (as in Bug#44744).

3. When reading out the page number for the overflow page this has a "wildly wrong value" (same as Bug#44744) representing a page that long way past the end of the file.

Setting the status to verified. Most likely this is a duplicate of Bug44744 but keep it this open until Bug44744 is fixed.
[12 Jun 2009 13:34] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:


2727 Olav Sandstaa	2009-06-12
      In Bug#44744 and Bug#45297 a crash occures during recovery. In both
      these cases the crash occurs when a record in a data page is attempted
      updated and the record is not already present in the page. This patch
      does not solve this problem but will make the recovery fail when the
      invalid update to the data page occurs instead of failing later when
      the invalid data is used.
      Common for both recovery crashes is that DataPage::updateRecord() is
      called with a lineNumber that is equal to the page's maxLine. This is
      not a correct use of this function as DataPage::updateRecord should 
      only be called for already existing records (ie. lineNumber should be
      less than maxLine).
      Through repeatedly running recovery I see several cases where this
      happens but does not lead to a crash but instead likely leads to an
      inconsistency. To avoid this inconsistency and to make the recovery
      fail immediately instead of when the invalid data is used this patch
      adds an ASSERT that verify that the lineNumber is valid.
[12 Jun 2009 13:51] Kevin Lewis
The assert is approved to help isolate this problem and protect from related problems.
[22 Jun 2009 12:28] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:


2739 Olav Sandstaa	2009-06-22
      Fix for Bug#44744 "Recovery stage 3: segfault in RecoveryObjects::findRecoveryObject" and Bug#45297 "Crash
      during recovery due to pread reading beyond EOF"
      These crashes was both caused by an inconsistency between the Record Locator Page and the Data page. The record 
      locator page claimed that the record was stored in a data page while the record was not present in the data page.
      This situation can happen during recovery if the Record Locator page has been written to disk while the 
      data page has not been written to disk when a server crash occurs. The recovery crash happened when the code
      had locate the record by a lookup in the Record Locator page and then called DataPage::updateRecord() where the
      record was not present. In the crash situation the record expected to be located on the same line number as
      the maxLine of the data page. This lead to reading "garbage" from the data page and resulted in an invalid 
      overflow page number.
      This patch fixes this problem by handling that DataPage::updateRecord and DataPage::deleteLine handles to
      be called also when the record is not present in the data page. In this situation both the functions will
      just ignore the call. DataPage::updateRecord() will return that there was not room for the record. This will
      result in the inconsistency between the data page and the Record Locator page being resolved since 
      the "failing" call to DataPage::updateRecord() will trigger removal of the record's entry in the Record Locator 
      page - and the record will be inserted somewhere else.
     @ storage/falcon/DataPage.cpp
        During recovery: extend DataPage::updateRecord() and DataPage::deleteLine() so that they handle to
        be called with a line number that is equal or larger than the current maxLine. If this is the case
        the call will just be ignored.
[22 Jun 2009 13:36] Kevin Lewis
Ann Harrison wrote;
The design of recovery is that changes made in phase 2 must be on their
original pages because they are referenced elsewhere by page number.
Changes made in phase 3 (including storing records) should indifferent
to the page they go on, as long as the page was free - or allocated
for the purpose for which it is reused.

So, I think 2B is OK, and probably follows the original design.
There's no requirement that record end up on their original page,
just that they still have the same record number