Dual Xeon 2.8 GHz, hyperthreaded, 533 MHz FSB 2 GB RAM Red Hat, kernel-2.4.20-18.9 SMP mysql 4.0.13, InnoDB table holding 32 million+ records, building an index using:
create index BY_NAME on PROFILE_NAMES (LAST_NAME,FIRST_NAME) my.cnf contains: [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock set-variable = innodb_buffer_pool_size=1400M set-variable = innodb_additional_mem_pool_size=80M [mysql.server] user=mysql basedir=/var/lib [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid [client] socket=/var/lib/mysql/mysql.sock tail of mysqld.lg contains: ============================ InnoDB: Warning: a long semaphore wait: --Thread 1103449392 has waited at btr0cur.c line 390 for 625.00 seconds the semaphore: X-lock on RW-latch at 9edf8384 created in file buf0buf.c line 369 a writer (thread id 1103449392) has reserved it in mode exclusive number of readers 0, waiters flag 1 Last time read locked in file buf0flu.c line 461 Last time write locked in file buf0buf.c line 1329 InnoDB: Error: semaphore wait has lasted > 600 seconds InnoDB: We intentionally crash the server, because it appears to be hung. 030702 10:41:11 InnoDB: Assertion failure in thread 2771143984 in file sync0arr.c line 934 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] InnoDB: Thread 2745965872 stopped in file os0file.c line 2386 InnoDB: Thread 2779536688 stopped in file ../../innobase/include/sync0sync.ic line 109 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=8388600 read_buffer_size=131072 Number of processes running now: 0 030702 10:41:13 mysqld restarted 030702 10:41:14 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 15 4169734769 InnoDB: Doing recovery: scanned up to log sequence number 15 4169757455 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 30820473 row operations to undo InnoDB: Trx id counter is 0 146424832 030702 10:41:14 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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: Starting rollback of uncommitted transactions InnoDB: Rolling back trx with id 0 146424065, 30820473 rows to undo InnoDB: Progress in percents: 1 2030702 14:20:22 mysqld started 030702 14:20:24 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 15 4237789310 InnoDB: Doing recovery: scanned up to log sequence number 15 4243032064 InnoDB: Doing recovery: scanned up to log sequence number 15 4247158606 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 30221929 row operations to undo InnoDB: Trx id counter is 0 146424832 030702 14:20:25 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: Starting rollback of uncommitted transactions InnoDB: Rolling back trx with id 0 146424065, 30221929 rows to undo InnoDB: Progress in percents: 1 2 3 4
