Extended record part does not match reference

[Amit Saha]

With a 'debug-max' build of MySQL 6.0.8 and a 'bzr' build of PBXT, MTR fails with "failed: 1297: Got temporary error -1 'Extended record part does not match reference' from PBXT"

The 'var/log/master.err' file has the following entries:

090306 13:20:40 [Error] user_1 int xt_tab_load_ext_data(table_xt.cc:2350) -50: Extended record part does not match reference
090306 13:20:40 [Error] user_1 int xt_tab_load_ext_data(table_xt.cc:2350)

To reproduce:

Please find the attached test case, I used.

[Vladimir Kolesnikov (vkolesnikov)]

Hi Amit,

the test uses the following files:

'$MYSQLTEST_VARDIR/1ws2511.txt'
'$MYSQLTEST_VARDIR/temp.txt'

can you please attach them.

Thanks.

[Amit Saha (amit-saha)]

Hi Vladmir,

Please create 2 simple files and add few lines of text. IMO, that should be good to reproduce.

Thanks.

[Vladimir Kolesnikov (vkolesnikov)]

Thanks for the report!

[Vladimir Kolesnikov (vkolesnikov)]

Hi Amit,

I cannot reproduce this problem in a current version of PBXT. I suppose it was fixed as a part of some other fix. I used MySQL 6.0.9 and PBXT rev. 657. Can you please retest with this configuration?

Thanks,
Vladimir

[Paul McCullagh (paul-mccullagh)]

This bug has been fixed in the later RC release (PBXT 1.0.09 RC3). Various errors of this kind were caused due to the truncation of a data log during recovery. Truncation took place when a "gap" was found in the data log.

A gap is a unwritten record, in the data log. Gaps occurred due to bugs in the error handling when writing a data log record (in particular due to an out-of-space error on the disk).

These bugs have also been fixed. In addition, recover now no longer truncates the data logs. Instead the log scanner is able to skip gaps if they occur.