# IBDATA1 file filling up when trying to import mysqldump

**URL:** <https://forums.percona.com/t/ibdata1-file-filling-up-when-trying-to-import-mysqldump/5917>\
**Category:** Other MySQL® Questions\
**Created:** [October 6, 2017, 1:15pm UTC](https://forums.percona.com/t/ibdata1-file-filling-up-when-trying-to-import-mysqldump/5917 "2017-10-06T13:15:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mwillman](https://avatars.discourse-cdn.com/v4/letter/m/e19adc/32.png) [@mwillman](https://forums.percona.com/u/mwillman)\
**Post date:** [October 6, 2017, 1:15pm UTC](https://forums.percona.com/t/ibdata1-file-filling-up-when-trying-to-import-mysqldump/5917/1 "2017-10-06T13:15:54Z")

</div>

Hi I am hoping someone has an answer to this quesiton. I am trying to import a 22G database .sql file on a new server but when i try to either source it or just pipe it It filles the IBDATA file up and crashes the system Im talking 72Gigs of IBdata file on a brand new server. IS there an argument I can use during the dump or a setting for the database itself to keep the IBDATA file from filling up?

---

<div class="post-metadata">

**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\
**Post date:** [October 7, 2017, 1:51am UTC](https://forums.percona.com/t/ibdata1-file-filling-up-when-trying-to-import-mysqldump/5917/2 "2017-10-07T01:51:32Z")

</div>

Can you share my.cnf file to check existing settings and also share related error log entries to check for crash message. What version of MySQL you are using ?
