Error Importing MySQLdump File

[root@localhost ~]# cat /var/log/mariadb/mariadb.log

140710 06:43:55 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

140710  6:43:55 InnoDB: The InnoDB memory heap is disabled

140710  6:43:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins

140710  6:43:55 InnoDB: Compressed tables use zlib 1.2.7

140710  6:43:55 InnoDB: Using Linux native AIO

140710  6:43:55 InnoDB: Initializing buffer pool, size = 128.0M

140710  6:43:55 InnoDB: Completed initialization of buffer pool

InnoDB: The first specified data file ./ibdata1 did not exist:

InnoDB: a new database to be created!

140710  6:43:55  InnoDB: Setting file ./ibdata1 size to 10 MB

InnoDB: Database physically writes the file full: wait...

140710  6:43:55  InnoDB: Log file ./ib_logfile0 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile0 size to 5 MB

InnoDB: Database physically writes the file full: wait...

140710  6:43:55  InnoDB: Log file ./ib_logfile1 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile1 size to 5 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Doublewrite buffer not found: creating new

InnoDB: Doublewrite buffer created

InnoDB: 127 rollback segment(s) active.

InnoDB: Creating foreign key constraint system tables

InnoDB: Foreign key constraint system tables created

140710  6:43:55  InnoDB: Waiting for the background threads to start

140710  6:43:56 Percona XtraDB (http://www.percona.com) 5.5.37-MariaDB-34.0 started; log sequence number 0

140710  6:43:56 [Note] Plugin 'FEEDBACK' is disabled.

140710  6:43:56 [Note] Server socket created on IP: '0.0.0.0'.

140710  6:43:56 [Note] Event Scheduler: Loaded 0 events

140710  6:43:56 [Note] /usr/libexec/mysqld: ready for connections.

Version: '5.5.37-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server

140710  7:40:22  InnoDB: Assertion failure in thread 70366338281648 in file fil0fil.c line 5286

InnoDB: Failing assertion: node->n_pending > 0

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

140710  7:40:22 [ERROR] mysqld got signal 6 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed, 

something is definitely wrong and this may fail.

Server version: 5.5.37-MariaDB

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=1

max_threads=153

thread_count=1

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466717 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0x0 thread_stack 0x48000

/usr/libexec/mysqld(my_print_stacktrace-0x4c07a8)[0x222df618]

/usr/libexec/mysqld(handle_fatal_signal-0x985960)[0x21dee640]

[0x3fff92ae0478]

/lib64/libc.so.6(abort-0x182b94)[0x3fff921efe74]

/usr/libexec/mysqld(+0x9c4310)[0x221d4310]

/usr/libexec/mysqld(+0x9d2314)[0x221e2314]

/usr/libexec/mysqld(+0x91edc8)[0x2212edc8]

/lib64/libpthread.so.0(+0xc460)[0x3fff92a8c460]

/lib64/libc.so.6(clone-0xb9ee8)[0x3fff922be150]

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.

140710 07:40:22 mysqld_safe Number of processes running now: 0

140710 07:40:22 mysqld_safe mysqld restarted

140710  7:40:22 InnoDB: The InnoDB memory heap is disabled

140710  7:40:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins

140710  7:40:22 InnoDB: Compressed tables use zlib 1.2.7

140710  7:40:22 InnoDB: Using Linux native AIO

140710  7:40:22 InnoDB: Initializing buffer pool, size = 128.0M

140710  7:40:22 InnoDB: Completed initialization of buffer pool

140710  7:40:22 InnoDB: highest supported file format is Barracuda.

InnoDB: Log scan progressed past the checkpoint lsn 21478975

140710  7:40:22  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

InnoDB: Doing recovery: scanned up to log sequence number 26721792

InnoDB: Doing recovery: scanned up to log sequence number 28142371

InnoDB: 1 transaction(s) which must be rolled back or cleaned up

InnoDB: in total 2049 row operations to undo

InnoDB: Trx id counter is 500

140710  7:40:23  InnoDB: Starting an apply batch of log records to the database...

InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 140710  7:40:23  InnoDB: Assertion failure in thread 70366413123760 in file data0type.ic line 488

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

140710  7:40:23 [ERROR] mysqld got signal 6 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed, 

something is definitely wrong and this may fail.

Server version: 5.5.37-MariaDB

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=0

max_threads=153

thread_count=0

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466717 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0x0 thread_stack 0x48000

/usr/libexec/mysqld(my_print_stacktrace-0x4c07a8)[0x2260f618]

/usr/libexec/mysqld(handle_fatal_signal-0x985960)[0x2211e640]

[0x3fff95170478]

/lib64/libc.so.6(abort-0x182b94)[0x3fff9487fe74]

/usr/libexec/mysqld(+0x9ae328)[0x224ee328]

/usr/libexec/mysqld(+0xa2c504)[0x2256c504]

/usr/libexec/mysqld(+0xa1a70c)[0x2255a70c]

/usr/libexec/mysqld(+0xa1cd1c)[0x2255cd1c]

/usr/libexec/mysqld(+0x9827bc)[0x224c27bc]

/usr/libexec/mysqld(+0x9d2478)[0x22512478]

/usr/libexec/mysqld(+0x91edc8)[0x2245edc8]

/lib64/libpthread.so.0(+0xc460)[0x3fff9511c460]

/lib64/libc.so.6(clone-0xb9ee8)[0x3fff9494e150]

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.

140710 07:40:23 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended