# Innodb NOT inserting rows but rows ending up in binlog

**URL:** <https://forums.percona.com/t/innodb-not-inserting-rows-but-rows-ending-up-in-binlog/1256>\
**Category:** Other MySQL® Questions\
**Created:** [September 8, 2009, 4:45pm UTC](https://forums.percona.com/t/innodb-not-inserting-rows-but-rows-ending-up-in-binlog/1256 "2009-09-08T16:45:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hramalho](https://avatars.discourse-cdn.com/v4/letter/h/5daacb/32.png) [@hramalho](https://forums.percona.com/u/hramalho)\
**Post date:** [September 8, 2009, 4:45pm UTC](https://forums.percona.com/t/innodb-not-inserting-rows-but-rows-ending-up-in-binlog/1256/1 "2009-09-08T16:45:35Z")

</div>

Hello,

We ran into an interesting problem the other day, when our production database stopped inserting row into a given table even though from the clients perspective they were inserted. What makes this even stranger is that the binlog recorded these “phantom” rows which then ended up on the slave. So the Slave actually have the valid data which was missing from the Master.

After playing for a bit, I notice that the given table was not locked, i.e. I could insert row into it. However, these rows were inserted into the next available row in the Master database, i.e. it did not skip over these phantom row. So this leads me to believe that it is some problem with InnoDB but I cannot figure out how this could have happened. Below is the table status for the table that locked up. Thanks in advance for any help.

Name: fileInfo  
Engine: InnoDB  
Version: 10  
Row\_format: Compact  
Rows: 4366226  
Avg\_row\_length: 3189  
Data\_length: 13925089280  
Max\_data\_length: 0  
Index\_length: 1303396352  
Data\_free: 0  
Auto\_increment: 5907230  
Create\_time: 2009-09-04 19:27:39  
Update\_time: NULL  
Check\_time: NULL  
Collation: utf8\_general\_ci  
Checksum: NULL  
Create\_options:  
Comment: InnoDB free: 4096 kB; (`shareId`) REFER `as_prod/share`(`id`); (`userId`) REFER

---

<div class="post-metadata">

**Author:** ![sterin71](https://avatars.discourse-cdn.com/v4/letter/s/5e9695/32.png) [@sterin71](https://forums.percona.com/u/sterin71)\
**Post date:** [September 9, 2009, 4:10pm UTC](https://forums.percona.com/t/innodb-not-inserting-rows-but-rows-ending-up-in-binlog/1256/2 "2009-09-09T16:10:43Z")

</div>

Do you have any errors in your error log file?

Has the MySQL process died or has the master server rebooted during this time?

How large is your database?  
Do you have any filesystem file size limitation that you may have hit for the InnoDB tablespace on the master?
