corruption in the InnoDB tablespace

[Manoj]

Hi All,

We are using Percona xtrabackup very extensively in our production
Mysql. We have Mysql 5.5 and xtrabackup was working fine 2 days back
but now we are seeing some corruption in the InnoDB tablespace.

We are getting below error when we run the xtrabackup. We checked
table using check table command and it seems to be ok to us. Kindly
suggest ???

[root@test]# mysql -Bse "check table access_db.access_history_14;"
access_db.access_history_14 check status OK



[07] Copying ./access_db/access_history_14.ibd
to /mnt/Storage/test/2012-04-16_07-10-24/access_db/
access_history_14.ibd
InnoDB: Error: tried to read 1048576 bytes at offset 0 2361393152.
InnoDB: Was only able to read 0.
InnoDB: Fatal error: cannot read from file. OS error number 17.
120416 7:20:44 InnoDB: Assertion failure in thread 1343990080 in
file /home/buildbot/slaves/percona-server-51-12/RPM_CentOS_5_x86_64/
work/BUILD/xtrabackup-1.6.2/Percona-Server-5.5/storage/innobase/os/
os0file.c line 2566
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
innobackupex-1.5.1: Error: ibbackup child process has died at /usr/bin/
innobackupex-1.5.1 line 336.

Thanks
Manoj

[Alexey Kopytov]

Manoj,

On 16.04.12 18:36, Manoj wrote:
> Hi All,
>
> We are using Percona xtrabackup very extensively in our production
> Mysql. We have Mysql 5.5 and xtrabackup was working fine 2 days back
> but now we are seeing some corruption in the InnoDB tablespace.
>
> We are getting below error when we run the xtrabackup. We checked
> table using check table command and it seems to be ok to us. Kindly
> suggest ???
>

We have a couple of similar bug reports, and are currently investigating
them. The problem seems to be specific to the --parallel option, so the
workaround is to not use parallel backups until this problem is fixed.

Best regards,
Alexey.

[Manoj Chauhan]

Hi Alexey,

Thanks for swift response. But this option was working fine 2 days back. Even another server same option is working.

Thanks
Manoj 

--
You received this message because you are subscribed to the Google Groups "Percona Discussion" group.
To post to this group, send email to percona-d...@googlegroups.com.
To unsubscribe from this group, send email to percona-discuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/percona-discussion?hl=en.