# Innodb Log File 4G limit?

**URL:** <https://forums.percona.com/t/innodb-log-file-4g-limit/1352>\
**Category:** Other MySQL® Questions\
**Created:** [February 17, 2010, 4:49pm UTC](https://forums.percona.com/t/innodb-log-file-4g-limit/1352 "2010-02-17T16:49:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![evilangel81](https://avatars.discourse-cdn.com/v4/letter/e/eada6e/32.png) [@evilangel81](https://forums.percona.com/u/evilangel81)\
**Post date:** [February 17, 2010, 4:49pm UTC](https://forums.percona.com/t/innodb-log-file-4g-limit/1352/1 "2010-02-17T16:49:45Z")

</div>

I am runnning:

mysql Ver 14.14 Distrib 5.1.37, for unknown-linux-gnu (x86\_64) using readline 5.1

But if i try to make my combined log file size \> 4GB mysql shuts down in such a way I would think its a 32bit machien unable to handle files larger than 4GB. Is this correct?

Also out system is running 32G of ram and Im only using 16G for my buffer pool. So I should have my logs at 8G minimum right? We are a right heavy company. And our Innodb Seq grows at aprox 14.5GBpH.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)\
**Post date:** [February 19, 2010, 9:48am UTC](https://forums.percona.com/t/innodb-log-file-4g-limit/1352/2 "2010-02-19T09:48:48Z")

</div>

You are following instructions that are wrong. Ratios are not the right way to calculate your log file size. See:

[http://www.mysqlperformanceblog.com/2008/11/21/how-to-calcul](http://www.mysqlperformanceblog.com/2008/11/21/how-to-calcul) ate-a-good-innodb-log-file-size/

See also:

[http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration](http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration). html

Note:

“The combined size of the log files must be less than 4GB.” This is an InnoDB limitation. If you are truly writing that much data per hour, I suspect you are doing something in a way that is not optimal for InnoDB, such as storing BLOB in the database.

---

<div class="post-metadata">

**Author:** ![evilangel81](https://avatars.discourse-cdn.com/v4/letter/e/eada6e/32.png) [@evilangel81](https://forums.percona.com/u/evilangel81)\
**Post date:** [April 21, 2010, 8:42am UTC](https://forums.percona.com/t/innodb-log-file-4g-limit/1352/3 "2010-04-21T08:42:11Z")

</div>

Generally I would agree with [http://dev.mysql.com/doc/innodb-plugin/1.1/en/innodb-perform](http://dev.mysql.com/doc/innodb-plugin/1.1/en/innodb-perform) ance-aio-linux.html being a good article but if you have large LOAD queries like loading very large email suppression lists into tables, its not really a good measure. For example with our system at 2G LOG files sizes i still get warning from time to time about a single log not being large enough to fit all the data. But I cant really grow the logs much more since there is the 4G limit. I thought the limit was supposed to be removed for 64bit machines but as of yet I have not seen that happen.