# Bug after restore backup by Xtrabackup **URL:** \ **Category:** Percona XtraBackup\ **Created:** [January 30, 2013, 10:25am UTC](https://forums.percona.com/t/bug-after-restore-backup-by-xtrabackup/2328 "2013-01-30T10:25:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![lampmanager](https://avatars.discourse-cdn.com/v4/letter/l/bc8723/32.png) [@lampmanager](https://forums.percona.com/u/lampmanager)\ **Post date:** [January 30, 2013, 10:25am UTC](https://forums.percona.com/t/bug-after-restore-backup-by-xtrabackup/2328/1 "2013-01-30T10:25:16Z")
After restoring all looks good - reading was ok, but after I starting inserts and updates I have mysqld signal 6 And now I have restart mysqld every 11 sec. I have tried 2 servers with percona 5.5, 5.1. Result was the same. I believe something wrong with one of tables. But I couldn’t find out it. Do you know what the problem? mysqld.log 130130 9:48:39 InnoDB: Warning: allocated tablespace 21, old maximum was 9130130 9:48:39 InnoDB: Assertion failure in thread 140639204140800 in file btr/btr0cur.c line 321InnoDB: Failing assertion: btr\_page\_get\_prev(get\_block-\>frame, mtr) == page\_get\_page\_no(page)InnoDB: We intentionally generate a memory trap.InnoDB: Submit a detailed bug report to .InnoDB: If you get repeated assertion failures or crashes, evenInnoDB: immediately after the mysqld startup, there may beInnoDB: corruption in the InnoDB tablespace. Please refer toInnoDB: about forcing recovery.15:48:39 UTC - mysqld got signal 6 ;This could be because you hit a bug. It is also possible that this binaryor one of the libraries it was linked against is corrupt, improperly built,or misconfigured. This error can also be caused by malfunctioning hardware.We will try our best to scrape up some info that will hopefully helpdiagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.Please help us make Percona Server better by reporting anybugs at key\_buffer\_size=209715200read\_buffer\_size=8388608max\_used\_connections=0max\_threads=400thread\_count=0connection\_count=0It is possible that mysqld could use up to key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 16593237 K bytes of memoryHope that’s ok; if not, decrease some variables in the equation.Thread pointer: 0x0Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong…stack\_bottom = 0 thread\_stack 0x80000/usr/sbin/mysqld(my\_print\_stacktrace+0x35)[0x8ac755]/usr/sbin/mysqld(handle\_fatal\_signal+0x40b)[0x6a862b]/lib64/libpthread.so.0(+0xf500)[0x7feac550e500]/lib64/libc.so.6(gsignal+0x35)[0x7feac46be8a5]/lib64/libc.so.6(abort+0x175)[0x7feac46c0085]/usr/sbin/mysqld[0x7ed8bd]/usr/sbin/mysqld[0x7f2ad0]/usr/sbin/mysqld[0x7a0c68]/usr/sbin/mysqld[0x79f502]/usr/sbin/mysqld[0x79fa16]/usr/sbin/mysqld[0x7a0558]/usr/sbin/mysqld[0x787680]/usr/sbin/mysqld[0x7bf3f6]/usr/sbin/mysqld[0x7b727b]/lib64/libpthread.so.0(+0x7851)[0x7feac5506851]/lib64/libc.so.6(clone+0x6d)[0x7feac477411d]You may download the Percona Server operations manual by visiting. You may find informationin the manual which will help you identify the cause of the crash.130130 09:48:39 mysqld\_safe Number of processes running now: 0130130 09:48:39 mysqld\_safe mysqld restarted Server version: 5.1.67-rel14.3-log Percona Server (GPL), 14.3, Revision 506 long\_query\_time = 1.5slow\_query\_log = 0slow\_query\_log\_file = /var/log/mysql/mysql-slow.logexpire\_logs\_days = 5basedir = /usrtmpdir = /tmpskip-external-lockingskip-name-resolveserver-id = 128## \* Fine Tuning#key\_buffer = 200Msort\_buffer\_size = 32Mread\_buffer\_size = 8Mtmp\_table\_size = 20Mmax\_heap\_table\_size = 20Mmax\_allowed\_packet = 16Mthread\_stack = 512Kthread\_cache\_size = 1200max\_connections = 400net\_read\_timeout=300net\_write\_timeout=300wait\_timeout=1800table\_cache = 1200table\_definition\_cache = 4096thread\_concurrency = 16## \* Query Cache Configuration#query\_cache\_limit = 1Mquery\_cache\_size = 32Mquery\_cache\_min\_res\_unit = 1024query\_cache\_wlock\_invalidate = ONinnodb\_file\_per\_tableinnodb\_buffer\_pool\_size=6000Minnodb\_file\_io\_threads=4innodb-thread-concurrency=0innodb\_log\_buffer\_size = 16Minnodb\_force\_recovery = 0innodb\_doublewrite=0innodb\_flush\_method=O\_DIRECTinnodb\_flush\_log\_at\_trx\_commit=0thread\_cache = 16delay\_key\_write = ALLbulk\_insert\_buffer\_size = 256M# Disabling symbolic-links is recommended to prevent assorted security riskssymbolic-links=1 Thank you for your help! ---
**Author:** ![niljoshi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/niljoshi/32/16889_2.png) [@niljoshi](https://forums.percona.com/u/niljoshi)\ **Post date:** [February 1, 2013, 12:10am UTC](https://forums.percona.com/t/bug-after-restore-backup-by-xtrabackup/2328/2 "2013-02-01T00:10:54Z")
Hi, Can you provide the Xtrabackup/Innobackupex version and the steps which you had taken to take and restore backup? (xtrabackup command lines). You might be hitting this bug. [URL][https://bugs.launchpad.net/percona-xtrabackup/+bug/776914[/URL]](https://bugs.launchpad.net/percona-xtrabackup/+bug/776914%5B/URL%5D) ---
**Author:** ![lampmanager](https://avatars.discourse-cdn.com/v4/letter/l/bc8723/32.png) [@lampmanager](https://forums.percona.com/u/lampmanager)\ **Post date:** [February 1, 2013, 5:43am UTC](https://forums.percona.com/t/bug-after-restore-backup-by-xtrabackup/2328/3 "2013-02-01T05:43:58Z")
xtrabackup version 2.0.3 for Percona Server 5.1.59 unknown-linux-gnu (x86\_64) (revision id: 470) Source server 1)xtrabackup --backup --tables=db.\* --target-dir=/newserv/export 2)xtrabackup --prepare --export --use-memory=1G --target-dir=/newserv/export Destination server Just copy to new SSD-disk withour raid and import to 5.1.67-rel14.3-log Percona Server After writing data to db I have got infinite errors and after 12 sec mysqld restarted I have suspicion to not correct tables. Tables can be +7 GB till 50 GB