MySQL Bugs: #43047: Error - "InnoDB: CORRUPT LOG RECORD FOUND" while taking backup using innobackup.

Bug #43047	Error - "InnoDB: CORRUPT LOG RECORD FOUND" while taking backup using innobackup.
Submitted:	20 Feb 2009 8:57	Modified:	6 Apr 2009 16:15
Reporter:	Nilesh Patil	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.1	OS:	FreeBSD
Assigned to:		CPU Architecture:	Any
Tags:	innodb CORRUPT LOG RECORD FOUND

Description:
When I tried to backup database on mysql, it does complete backup but with this details.

InnoDB: ############### CORRUPT LOG RECORD FOUND
InnoDB: Log record type 37, space id 0, page number 54
InnoDB: Log parsing proceeded successfully up to 457 3180151325
InnoDB: Previous log record type 4, is multi 1
InnoDB: Recv offset 147858, prev 147852
InnoDB: Hex dump of corrupt log starting 100 bytes before the start
InnoDB: of the previous log rec,
InnoDB: and ending 100 bytes after the start of the corrupt rec:
len 206; hex ff0400d340320316f0ffffffff0400d34032031af0ffffffff0400d34032031ef0ffffffff0400d340320322f0ffffffff0400d340320326f0ffffffff0400d34032032af0ffffffff0400d34032032ef0ffffffff02003600528272040036004ed34032040036004a0025003608003600420000000028020036004000040036000cf0ffffffff0400360008f0ffffffff04000b029f361f82003400380219003500cb2d978f02003500289090020035002a90900200350fe890901f94003501501c000e0000cb2d92be0000371c; asc ....@2..........@2..........@2..........@2."........@2.&........@2.*........@2.........6.R.r..6.N.@2..6.J.%.6..6.B....(..6.@...6.........6............6...4.8...5..-....5.(....5.*....5.......5.P......-....7.;
InnoDB: WARNING: the log file may have been corrupt and it
InnoDB: is possible that the log scan did not proceed
InnoDB: far enough in recovery! Please run CHECK TABLE
InnoDB: on your InnoDB tables to check that they are ok!
InnoDB: If mysqld crashes after this recovery, look at
InnoDB: section 6.1 of http://www.innodb.com/ibman.html
InnoDB: about forcing recovery.
090217 12:09:37 ibbackup: FOUND CORRUPT LOG: cannot continue!
innobackup: All tables locked and flushed to disk 

When I tried to use that backup for replication it returns following error. 
 93100 93200 93300 93400 93500 93600 93700 93800 93900 94000 94100 94200 94300 94400 94500 94600 94700 94800 94900 95000 95100 95200 95300 95400 95500 95600 95700 95800 95900 96000 96100 96200 96300 96400 96500 96600 96700 96800 96900 97000 97100 97200 97300 97400 97500 97600 97700 97800 97900 98000 98100 98200 98300 98400 98500 98600 98700 98800 98900 99000 99100
090217  6:06:53  ibbackup: ibbackup_logfile's creation parameters:
ibbackup: start lsn 2741414182 13434992, end lsn 238527 0,
ibbackup: start checkpoint 0 0
ibbackup: Error: backed up log file segment has a wrong magic n:o 0.
ibbackup: Run 'ibbackup --help' for help.
innobackup: Error:
innobackup: ibbackup failed at /home/y/var/bin//innobackup line 33

Please suggest me something. 

Thanks,
Nilesh

How to repeat:
1. Have a innodb database. 
2. trying to backup using innobackup tool.

Thank you for the report.

I assume you have problems running InnoDB Hot Backup. If so this can be problem of this tool. MySQL does not maintain InnoDB Hot Backup, so, please open a report at innodb.com

But if you think this is not bug of InnoDB Hot Backup, but something goes wrong with MySQL server itself please send us full server error log file.

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

Problem is still persist.
I checked mysql logs where i can not find anything related to innodb backup. And yes I am using innodb hot backup tool. I checked ther manual and official site, can not find details. 

Thanks,
Nilesh

Thank you for the feedback.

> And yes I am using innodb hot backup tool.

I assume in the initial description you provided output of this tool. Please also report this problem here: http://forums.innodb.com/list.php?6

> I checked mysql logs where i can not find anything related to innodb backup.

You should not: mysql server and InnoDB Hot Backup are different products. But error log can contain information about problems with MySQL server. This is why we need full error log file.

Reported problem on the innodb forum too.
http://forums.innodb.com/read.php?6,477,477#msg-477

there is nothing as such in mysql logs. 

Thanks,
Nilesh

Thank you for the feedback.

> there is nothing as such in mysql logs. 

So this looks like not a MySQL bug and I close the report as such.

Please continue discussion at InnoDB forums and if they found problem is MySQL feel free to reopen this report.