# innobackupex failed at fil\_cur.cc:293

**URL:** <https://forums.percona.com/t/innobackupex-failed-at-fil-cur-cc-293/3276>\
**Category:** Percona XtraBackup\
**Created:** [February 13, 2014, 10:43pm UTC](https://forums.percona.com/t/innobackupex-failed-at-fil-cur-cc-293/3276 "2014-02-13T22:43:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sevmax](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sevmax](https://forums.percona.com/u/sevmax)\
**Post date:** [February 13, 2014, 10:43pm UTC](https://forums.percona.com/t/innobackupex-failed-at-fil-cur-cc-293/3276/1 "2014-02-13T22:43:59Z")

</div>

Hello,  
I have been using innobackupex for a while on a number of databases, but today I faced an issue which I haven’t seen before.  
During initial backup of 470Gb MySQL database innobackupex fails with the following error:

> [@](#):
>
> Assertion “to\_read % cursor-&gt;page\_size == 0” failed at fil\_cur.cc:293  
> Aborted  
> innobackupex: Error: The xtrabackup child process has died at /usr/bin/innobackupex line 2642.

I tried to make a backup on a local disk, on nfs mount and using nc. I tried to do it in tar.gz, tar and raw files.  
Every time it failed somewhere at the end of the backup process, because resulted files are almost the same size as an initial ones.

> [@](#):
>
> Ubuntu 12.04 LTS
> 
> # uname -a
> 
> Linux mysql1 3.5.0-45-generic #68~precise1-Ubuntu SMP Wed Dec 4 16:18:46 UTC 2013 x86\_64 x86\_64 x86\_64 GNU/Linux
> 
> # mysql --version
> 
> mysql Ver 14.14 Distrib 5.5.35, for debian-linux-gnu (x86\_64) using readline 6.2
> 
> # innobackupex --version
> 
> InnoDB Backup Utility v1.5.1-xtrabackup
> 
> # xtrabackup --version
> 
> xtrabackup version 2.1.7 for Percona Server 5.1.73 unknown-linux-gnu (x86\_64) (revision id: 721)

Appreciate any help there.  
Thank you.

---

<div class="post-metadata">

**Author:** ![jrivera](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jrivera/32/13_2.png) [@jrivera](https://forums.percona.com/u/jrivera)\
**Post date:** [February 16, 2014, 7:56pm UTC](https://forums.percona.com/t/innobackupex-failed-at-fil-cur-cc-293/3276/2 "2014-02-16T19:56:49Z")

</div>

By any chance you might be affected by this bug [URL][https://bugs.launchpad.net/percona-xtrabackup/+bug/1177201[/URL]](https://bugs.launchpad.net/percona-xtrabackup/+bug/1177201%5B/URL%5D)

---

<div class="post-metadata">

**Author:** ![sevmax](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sevmax](https://forums.percona.com/u/sevmax)\
**Post date:** [February 19, 2014, 7:36pm UTC](https://forums.percona.com/t/innobackupex-failed-at-fil-cur-cc-293/3276/3 "2014-02-19T19:36:47Z")

</div>

Thank you.  
It is exactly what you have highlighted.  
I have found the workaround for this issue: [URL=“[Percona XtraBackup – A workaround for failed assertion bug](http://www.mysqlperformanceblog.com/2013/11/27/percona-xtrabackup-a-workaround-for-failed-assertion-bug/)”][http://www.mysqlperformanceblog.com/...assertion-bug/[/URL]](http://www.mysqlperformanceblog.com/...assertion-bug/%5B/URL%5D)  
We are optimizing our database in order reduce used space and run “Alter table” or “Optimize” commands, since they will take a long time.

---

<div class="post-metadata">

**Author:** ![sevmax](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sevmax](https://forums.percona.com/u/sevmax)\
**Post date:** [February 22, 2014, 5:46pm UTC](https://forums.percona.com/t/innobackupex-failed-at-fil-cur-cc-293/3276/4 "2014-02-22T17:46:42Z")

</div>

As an update: Method I have mentioned on my previous post helped me.  
This issue is solved.
