Mani Sundarigari added a comment - 2013-01-26 19:25 $ cat /fisc/dba/mani/mysql/data/vlmmk644.err 130126 12:23:39 mysqld_safe Starting mysqld daemon with databases from /fisc/dba/mani/mysql/data 130126 12:23:39 InnoDB: The InnoDB memory heap is disabled 130126 12:23:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins 130126 12:23:39 InnoDB: Compressed tables use zlib 1.2.3 130126 12:23:39 InnoDB: Using Linux native AIO 130126 12:23:39 InnoDB: CPU supports crc32 instructions 130126 12:23:39 InnoDB: Error: Linux Native AIO is not supported on tmpdir. InnoDB: You can either move tmpdir to a file system that supports native AIO InnoDB: or you can set innodb_use_native_aio to FALSE to avoid this message. 130126 12:23:39 InnoDB: Error: Linux Native AIO check on tmpdir returned error [22] 130126 12:23:39 InnoDB: Warning: Linux Native AIO disabled. 130126 12:23:39 InnoDB: Initializing buffer pool, size = 128.0M 130126 12:23:39 InnoDB: Completed initialization of buffer pool 130126 12:23:39 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 130126 12:23:39 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... 130126 12:23:39 InnoDB: Assertion failure in thread 47234847274368 in file fsp0fsp.cc line 1964 InnoDB: Failing assertion: inode 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/MYSQL_VERSION_MAJOR.MYSQL_VERSION_MINOR/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 130126 12:23:39 [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: 10.0.0-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 = 466394 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 mysys/stacktrace.c:247(my_print_stacktrace) [0xad87be] sql/signal_handler.cc:153(handle_fatal_signal) [0x6db142] :0( ) [0x325160ebe0] :0( ) [0x3250630265] :0( ) [0x3250631d10] fsp/fsp0fsp.cc:1964(fseg_inode_get(unsigned char*, unsigned long, unsigned long, mtr_struct*)) [0xa37f7b] fsp/fsp0fsp.cc:2295(fseg_n_reserved_pages(unsigned char*, unsigned long*, mtr_struct*)) [0xa38755] ibuf/ibuf0ibuf.cc:546(ibuf_init_at_db_start()) [0x93a7b1] dict/dict0boot.cc:459(dict_boot()) [0xa0b89b] srv/srv0start.cc:2071(innobase_start_or_create_for_mysql()) [0x9af441] handler/ha_innodb.cc:3048(innobase_init) [0x91aa8a] sql/handler.cc:467(ha_initialize_handlerton(st_plugin_int*)) [0x6dd2b8] sql/sql_plugin.cc:1356(plugin_initialize) [0x593876] sql/sql_plugin.cc:1597(plugin_init(int*, char**, int)) [0x5947d9] sql/mysqld.cc:4399(init_server_components) [0x505571] sql/mysqld.cc:4967(mysqld_main(int, char**)) [0x507eec] :0( ) [0x325061d994] ??:0(_start) [0x4fcf49] 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. 130126 12:23:40 mysqld_safe mysqld from pid file /fisc/dba/mani/mysql/data/vlmmk644.pid ended $

Elena Stepanova added a comment - 2013-01-26 19:44 130126 12:08:43 InnoDB: Error: all log files must be created at the same time. 130126 12:08:43 InnoDB: All log files must be created also in database creation. 130126 12:08:43 InnoDB: If you want bigger or smaller log files, shut down the 130126 12:08:43 InnoDB: database and make sure there were no errors in shutdown. 130126 12:08:43 InnoDB: Then delete the existing log files. Edit the .cnf file 130126 12:08:43 InnoDB: and start the database again.