050921 10:49:24 mysqld started InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 050921 10:49:24 InnoDB: Setting file ./ibdata1 size to 10240 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000 2100 2200 2300 2400 2500 2600 2700 2800 2900 3000 3100 3200 3300 3400 3500 3600 3700 3800 3900 4000 4100 4200 4300 4400 4500 4600 4700 4800 4900 5000 5100 5200 5300 5400 5500 5600 5700 5800 5900 6000 6100 6200 6300 6400 6500 6600 6700 6800 6900 7000 7100 7200 7300 7400 7500 7600 7700 7800 7900 8000 8100 8200 8300 8400 8500 8600 8700 8800 8900 9000 9100 9200 9300 9400 9500 9600 9700 9800 9900 10000 10100 10200 050921 10:53:24 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 256 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 050921 10:53:32 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 256 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 050921 10:53:41 InnoDB: Log file ./ib_logfile2 did not exist: new to be created InnoDB: Setting log file ./ib_logfile2 size to 256 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 050921 10:53:50 InnoDB: Started; log sequence number 0 0 050921 10:53:51 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.12-beta-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 050921 11:23:10InnoDB: Assertion failure in thread 1782098864 in file ibuf0ibuf.c line 2760 InnoDB: Failing assertion: trx_sys_multiple_tablespace_format 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/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. mysqld got signal 11; 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. 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. key_buffer_size=33554432 read_buffer_size=2093056 max_used_connections=1 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1056367 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a2f970 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... Cannot determine thread, fp=0x6a387b4c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8153640 0xffffe420 0x832b4ec 0x827c6f7 0x827cd6e 0x827ce9e 0x827ceef 0x827d11f 0x827f36e 0x81fdf56 0x81b0ed3 0x820fac8 0x820ebcd 0x81693ee 0x816ed90 0x816688e 0x81663dd 0x81658db 0x40051aa7 0x40182c2e New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x8a2b6a8 = LOAD DATA INFILE '/data/loaddata/lineitem.tbl' INTO TABLE lineitem FIELDS TERMINATED BY '|' LINES TERMINATED BY '|\n' thd->thread_id=7 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 050921 11:23:10 mysqld restarted 050921 11:23:11 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... 050921 11:23:11 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 1870995865. InnoDB: Doing recovery: scanned up to log sequence number 0 1876238336 InnoDB: Doing recovery: scanned up to log sequence number 0 1881481216 InnoDB: Doing recovery: scanned up to log sequence number 0 1886724096 InnoDB: Doing recovery: scanned up to log sequence number 0 1891966976 InnoDB: Doing recovery: scanned up to log sequence number 0 1897209856 InnoDB: Doing recovery: scanned up to log sequence number 0 1902452736 InnoDB: Doing recovery: scanned up to log sequence number 0 1907695616 InnoDB: Doing recovery: scanned up to log sequence number 0 1912938496 InnoDB: Doing recovery: scanned up to log sequence number 0 1918181376 InnoDB: Doing recovery: scanned up to log sequence number 0 1923424256 InnoDB: Doing recovery: scanned up to log sequence number 0 1928667136 InnoDB: Doing recovery: scanned up to log sequence number 0 1933910016 InnoDB: Doing recovery: scanned up to log sequence number 0 1939152896 InnoDB: Doing recovery: scanned up to log sequence number 0 1944395776 InnoDB: Doing recovery: scanned up to log sequence number 0 1949638656 InnoDB: Doing recovery: scanned up to log sequence number 0 1954881536 InnoDB: Doing recovery: scanned up to log sequence number 0 1960124416 InnoDB: Doing recovery: scanned up to log sequence number 0 1965367296 InnoDB: Doing recovery: scanned up to log sequence number 0 1970610176 InnoDB: Doing recovery: scanned up to log sequence number 0 1975853056 InnoDB: Doing recovery: scanned up to log sequence number 0 1981095936 InnoDB: Doing recovery: scanned up to log sequence number 0 1986338816 InnoDB: Doing recovery: scanned up to log sequence number 0 1991581696 InnoDB: Doing recovery: scanned up to log sequence number 0 1996824576 InnoDB: Doing recovery: scanned up to log sequence number 0 2002067456 InnoDB: Doing recovery: scanned up to log sequence number 0 2007310336 InnoDB: Doing recovery: scanned up to log sequence number 0 2012553216 InnoDB: Doing recovery: scanned up to log sequence number 0 2017796096 InnoDB: Doing recovery: scanned up to log sequence number 0 2023038976 InnoDB: Doing recovery: scanned up to log sequence number 0 2028281856 InnoDB: Doing recovery: scanned up to log sequence number 0 2033524736 InnoDB: Doing recovery: scanned up to log sequence number 0 2038767616 InnoDB: Doing recovery: scanned up to log sequence number 0 2044010496 InnoDB: Doing recovery: scanned up to log sequence number 0 2049253376 InnoDB: Doing recovery: scanned up to log sequence number 0 2054496256 InnoDB: Doing recovery: scanned up to log sequence number 0 2059739136 InnoDB: Doing recovery: scanned up to log sequence number 0 2064982016 InnoDB: Doing recovery: scanned up to log sequence number 0 2070224896 InnoDB: Doing recovery: scanned up to log sequence number 0 2075467776 InnoDB: Doing recovery: scanned up to log sequence number 0 2080710656 InnoDB: Doing recovery: scanned up to log sequence number 0 2085953536 InnoDB: Doing recovery: scanned up to log sequence number 0 2091196416 InnoDB: Doing recovery: scanned up to log sequence number 0 2096439296 InnoDB: Doing recovery: scanned up to log sequence number 0 2101682176 InnoDB: Doing recovery: scanned up to log sequence number 0 2106925056 InnoDB: Doing recovery: scanned up to log sequence number 0 2112167936 InnoDB: Doing recovery: scanned up to log sequence number 0 2117410816 InnoDB: Doing recovery: scanned up to log sequence number 0 2122653696 InnoDB: Doing recovery: scanned up to log sequence number 0 2127896576 InnoDB: Doing recovery: scanned up to log sequence number 0 2133139456 InnoDB: Doing recovery: scanned up to log sequence number 0 2138382336 InnoDB: Doing recovery: scanned up to log sequence number 0 2143625216 InnoDB: Doing recovery: scanned up to log sequence number 0 2148868096 InnoDB: Doing recovery: scanned up to log sequence number 0 2154110976 InnoDB: Doing recovery: scanned up to log sequence number 0 2159353856 InnoDB: Doing recovery: scanned up to log sequence number 0 2164596736 InnoDB: Doing recovery: scanned up to log sequence number 0 2169839616 InnoDB: Doing recovery: scanned up to log sequence number 0 2175082496 InnoDB: Doing recovery: scanned up to log sequence number 0 2180325376 InnoDB: Doing recovery: scanned up to log sequence number 0 2185568256 InnoDB: Doing recovery: scanned up to log sequence number 0 2190811136 InnoDB: Doing recovery: scanned up to log sequence number 0 2196054016 InnoDB: Doing recovery: scanned up to log sequence number 0 2201296896 InnoDB: Doing recovery: scanned up to log sequence number 0 2206539776 InnoDB: Doing recovery: scanned up to log sequence number 0 2211782656 050921 11:23:59 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 InnoDB: Apply batch completed InnoDB: Doing recovery: scanned up to log sequence number 0 2217025536 InnoDB: Doing recovery: scanned up to log sequence number 0 2222268416 InnoDB: Doing recovery: scanned up to log sequence number 0 2226925802 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1795557 row operations to undo InnoDB: Trx id counter is 0 1280 050921 11:25:04 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 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 0, file name InnoDB: Starting in background the rollback of uncommitted transactions 050921 11:25:27 InnoDB: Rolling back trx with id 0 942, 1795557 rows to undo InnoDB: Progress in percents: 1050921 11:25:27 InnoDB: Started; log sequence number 0 2226925802 050921 11:25:28 [ERROR] /usr/sbin/mysqld: Table './mysql/user' is marked as crashed and should be repaired 050921 11:25:28 [Warning] Checking table: './mysql/user' 050921 11:25:28 [ERROR] 1 client is using or hasn't closed the table properly 050921 11:25:28 [ERROR] /usr/sbin/mysqld: Table './mysql/db' is marked as crashed and should be repaired 050921 11:25:28 [Warning] Checking table: './mysql/db' 050921 11:25:28 [ERROR] 1 client is using or hasn't closed the table properly 050921 11:25:28 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.12-beta-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 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 100 InnoDB: Rolling back of trx id 0 942 completed 050921 11:26:34 InnoDB: Rollback of non-prepared transactions completed 050921 12:04:45InnoDB: Assertion failure in thread 1787067312 in file ibuf0ibuf.c line 2760 InnoDB: Failing assertion: trx_sys_multiple_tablespace_format 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/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. mysqld got signal 11; 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. 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. key_buffer_size=33554432 read_buffer_size=2093056 max_used_connections=1 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1056367 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x89fced8 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... Cannot determine thread, fp=0x6a844b4c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8153640 0xffffe420 0x6a8452ac 0x827c6f7 0x827cd6e 0x827ce9e 0x827ceef 0x827d11f 0x827f36e 0x81fdf56 0x81b0ed3 0x820fac8 0x820ebcd 0x81693ee 0x816ed90 0x816688e 0x81663dd 0x81658db 0x40051aa7 0x40182c2e New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x8a032f0 = LOAD DATA INFILE '/data/loaddata2/lineitem.tbl' INTO TABLE lineitem FIELDS TERMINATED BY '|' LINES TERMINATED BY '|\n' thd->thread_id=8 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 050921 12:04:45 mysqld restarted 050921 12:04:46 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... 050921 12:04:46 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 4271963463. InnoDB: Doing recovery: scanned up to log sequence number 0 4277206016 InnoDB: Doing recovery: scanned up to log sequence number 0 4282448896 InnoDB: Doing recovery: scanned up to log sequence number 0 4287691776 InnoDB: Doing recovery: scanned up to log sequence number 0 4292934656 InnoDB: Doing recovery: scanned up to log sequence number 1 3210240 InnoDB: Doing recovery: scanned up to log sequence number 1 8453120 InnoDB: Doing recovery: scanned up to log sequence number 1 13696000 InnoDB: Doing recovery: scanned up to log sequence number 1 18938880 InnoDB: Doing recovery: scanned up to log sequence number 1 24181760 InnoDB: Doing recovery: scanned up to log sequence number 1 29424640 InnoDB: Doing recovery: scanned up to log sequence number 1 34667520 InnoDB: Doing recovery: scanned up to log sequence number 1 39910400 InnoDB: Doing recovery: scanned up to log sequence number 1 45153280 InnoDB: Doing recovery: scanned up to log sequence number 1 50396160 InnoDB: Doing recovery: scanned up to log sequence number 1 55639040 InnoDB: Doing recovery: scanned up to log sequence number 1 60881920 InnoDB: Doing recovery: scanned up to log sequence number 1 66124800 InnoDB: Doing recovery: scanned up to log sequence number 1 71367680 InnoDB: Doing recovery: scanned up to log sequence number 1 76610560 InnoDB: Doing recovery: scanned up to log sequence number 1 81853440 InnoDB: Doing recovery: scanned up to log sequence number 1 87096320 InnoDB: Doing recovery: scanned up to log sequence number 1 92339200 InnoDB: Doing recovery: scanned up to log sequence number 1 97582080 InnoDB: Doing recovery: scanned up to log sequence number 1 102824960 InnoDB: Doing recovery: scanned up to log sequence number 1 108067840 InnoDB: Doing recovery: scanned up to log sequence number 1 113310720 InnoDB: Doing recovery: scanned up to log sequence number 1 118553600 InnoDB: Doing recovery: scanned up to log sequence number 1 123796480 InnoDB: Doing recovery: scanned up to log sequence number 1 129039360 InnoDB: Doing recovery: scanned up to log sequence number 1 134282240 InnoDB: Doing recovery: scanned up to log sequence number 1 139525120 InnoDB: Doing recovery: scanned up to log sequence number 1 144768000 InnoDB: Doing recovery: scanned up to log sequence number 1 150010880 InnoDB: Doing recovery: scanned up to log sequence number 1 155253760 InnoDB: Doing recovery: scanned up to log sequence number 1 160496640 InnoDB: Doing recovery: scanned up to log sequence number 1 165739520 InnoDB: Doing recovery: scanned up to log sequence number 1 170982400 InnoDB: Doing recovery: scanned up to log sequence number 1 176225280 InnoDB: Doing recovery: scanned up to log sequence number 1 181468160 InnoDB: Doing recovery: scanned up to log sequence number 1 186711040 InnoDB: Doing recovery: scanned up to log sequence number 1 191953920 InnoDB: Doing recovery: scanned up to log sequence number 1 197196800 InnoDB: Doing recovery: scanned up to log sequence number 1 202439680 InnoDB: Doing recovery: scanned up to log sequence number 1 207682560 InnoDB: Doing recovery: scanned up to log sequence number 1 212925440 InnoDB: Doing recovery: scanned up to log sequence number 1 218168320 InnoDB: Doing recovery: scanned up to log sequence number 1 223411200 InnoDB: Doing recovery: scanned up to log sequence number 1 228654080 InnoDB: Doing recovery: scanned up to log sequence number 1 233896960 InnoDB: Doing recovery: scanned up to log sequence number 1 239139840 InnoDB: Doing recovery: scanned up to log sequence number 1 244382720 InnoDB: Doing recovery: scanned up to log sequence number 1 249625600 InnoDB: Doing recovery: scanned up to log sequence number 1 254868480 InnoDB: Doing recovery: scanned up to log sequence number 1 260111360 InnoDB: Doing recovery: scanned up to log sequence number 1 265354240 InnoDB: Doing recovery: scanned up to log sequence number 1 270597120 InnoDB: Doing recovery: scanned up to log sequence number 1 275840000 InnoDB: Doing recovery: scanned up to log sequence number 1 281082880 InnoDB: Doing recovery: scanned up to log sequence number 1 286325760 InnoDB: Doing recovery: scanned up to log sequence number 1 291568640 InnoDB: Doing recovery: scanned up to log sequence number 1 296811520 InnoDB: Doing recovery: scanned up to log sequence number 1 302054400 InnoDB: Doing recovery: scanned up to log sequence number 1 307297280 InnoDB: Doing recovery: scanned up to log sequence number 1 312540160 InnoDB: Doing recovery: scanned up to log sequence number 1 317783040 050921 12:05:34 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 InnoDB: Apply batch completed InnoDB: Doing recovery: scanned up to log sequence number 1 323025920 InnoDB: Doing recovery: scanned up to log sequence number 1 328268800 InnoDB: Doing recovery: scanned up to log sequence number 1 333511680 InnoDB: Doing recovery: scanned up to log sequence number 1 338754560 InnoDB: Doing recovery: scanned up to log sequence number 1 343997440 InnoDB: Doing recovery: scanned up to log sequence number 1 349240320 InnoDB: Doing recovery: scanned up to log sequence number 1 349477124 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1799134 row operations to undo InnoDB: Trx id counter is 0 1792 050921 12:06:39 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 0, file name InnoDB: Starting in background the rollback of uncommitted transactions 050921 12:07:05 InnoDB: Rolling back trx with id 0 1479, 1799134 rows to undo InnoDB: Progress in percents: 1050921 12:07:05 InnoDB: Started; log sequence number 1 349477124 050921 12:07:05 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.12-beta-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 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 100 InnoDB: Rolling back of trx id 0 1479 completed 050921 12:08:13 InnoDB: Rollback of non-prepared transactions completed