MySQL Bugs: #71720: InnoDB: unable to purge a record

Bug #71720	InnoDB: unable to purge a record
Submitted:	14 Feb 2014 13:56	Modified:	22 Sep 2015 11:47
Reporter:	Carson Reinke	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.5.22, 5.6.16	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
Received this error message from a slave server.

140213 12:04:40  InnoDB: unable to purge a record
InnoDB: tuple DATA TUPLE: 5 fields;
 0: len 4; hex 8000000e; asc     ;;
 1: SQL NULL;
 2: len 35; hex 436c696e746f6e3a3a566f6c7573696f6e3a3a4a6f623a3a576f726b666c6f774a6f62; asc [some data];;
 3: SQL NULL;
 4: len 4; hex 83ba0fbc; asc     ;;

InnoDB: record PHYSICAL RECORD: n_fields 5; compact format; info bits 32
 0: len 4; hex 8000000e; asc     ;;
 1: SQL NULL;
 2: len 30; hex 436c696e746f6e3a3a566f6c7573696f6e3a3a4a6f623a3a576f726b666c; asc [some data]; (total 35 bytes);
 3: SQL NULL;
 4: len 4; hex 83ba0fbc; asc     ;;

space 790 offset 23002 (1 records, index id 2148)
InnoDB: Submit a detailed bug report to http://bugs.mysql.com

mysql> ANALYZE TABLE table\G
*************************** 1. row ***************************
   Table: table
      Op: analyze
Msg_type: status
Msg_text: OK

mysql> CHECK TABLE table\G
*************************** 1. row ***************************
   Table: table
      Op: check
Msg_type: status
Msg_text: OK
1 row in set (4 min 38.78 sec)

InnoDB status does not report anything unusual.  Please let me know any additional information I can provide.

How to repeat:
Unknown

Various fixes have been made in recent versions that might help this situation.
For example:
Bug 16628233 - CHANGE BUFFERING: CRASH/CORRUPTION, AFTER ERROR "UNABLE TO PURGE A RECORD" 
Bug 16183892 - INNODB PURGE BUFFERING IS NOT CRASH-SAFE

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".

Still hit with 5.6.16, just one master:

2014-07-08 17:36:56 2b1b0b501700  InnoDB: unable to purge a record
InnoDB: tuple DATA TUPLE: 17 fields;
 0: len 8; hex 80000000030103f0; asc         ;;
 1: len 8; hex 8000124f17de9fbd; asc    O    ;;
 2: len 1; hex 81; asc  ;;
 3: len 1; hex 80; asc  ;;
 4: len 4; hex 80000064; asc    d;;
 5: len 1; hex 87; asc  ;;
 6: SQL NULL;
 7: len 1; hex 82; asc  ;;
 8: SQL NULL;
 9: len 1; hex 84; asc  ;;
 10: len 8; hex 8000124f17de9fbd; asc    O    ;;
 11: len 8; hex 8000000001818618; asc         ;;
 12: SQL NULL;
 13: len 1; hex 81; asc  ;;
 14: SQL NULL;
 15: len 2; hex 8000; asc   ;;
 16: len 8; hex 8000000010f17782; asc       w ;;

InnoDB: record PHYSICAL RECORD: n_fields 17; compact format; info bits 32
 0: len 8; hex 80000000030103f0; asc         ;;
 1: len 8; hex 8000124f17de9fbd; asc    O    ;;
 2: len 1; hex 81; asc  ;;
 3: len 1; hex 80; asc  ;;
 4: len 4; hex 80000064; asc    d;;
 5: len 1; hex 87; asc  ;;
 6: SQL NULL;
 7: len 1; hex 82; asc  ;;
 8: SQL NULL;
 9: len 1; hex 84; asc  ;;
 10: len 8; hex 8000124f17de9fbd; asc    O    ;;
 11: len 8; hex 8000000001818618; asc         ;;
 12: SQL NULL;
 13: len 1; hex 81; asc  ;;
 14: SQL NULL;
 15: len 2; hex 8000; asc   ;;
 16: len 8; hex 8000000010f17782; asc       w ;;

space 66 offset 190655 (1 records, index id 150)

Please note, we still have one verified bug:
http://bugs.mysql.com/bug.php?id=70214

http://bugs.mysql.com/bug.php?id=74208 marked as duplicate of this one.

Please see if this is repeatable in 5.6.26.  There was a bugfix there that may have solved this.  http://bugs.mysql.com/bug.php?id=70214

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".