Bug #60976 | Crash, valgrind warning and memory leak with partitioned archive tables | ||
---|---|---|---|
Submitted: | 26 Apr 2011 8:48 | Modified: | 16 Jun 2011 19:17 |
Reporter: | Philip Stoev | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Archive storage engine | Severity: | S1 (Critical) |
Version: | 5.1, 5.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[26 Apr 2011 8:48]
Philip Stoev
[26 Apr 2011 9:30]
MySQL Verification Team
some related archive locking bugs: (but have not confirmed anything with partitions yet): bug #42784 (archive tables cause 100% cpu usage and hang in show table status) bug #37280 (check and repair table report table corrupted when run concurrently with inserts) bug #51252 (archive tables still fail under stress tests: crash, corruption, 4G memory alloc)
[26 Apr 2011 9:36]
Valeriy Kravchuk
Verified just as described with current mysql-5.1 on 32-bit Ubuntu 10.04: ... 110426 12:34:01 [Note] /home/openxs/dbs/5.1/libexec/mysqld: ready for connections. Version: '5.1.57-valgrind-max-debug' socket: '/tmp/mysql.sock' port: 3306 Source distribution mysqld: my_seek.c:58: my_seek: Assertion `fd != -1' failed. 110426 12:34:29 - 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. 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=8384512 read_buffer_size=131072 max_used_connections=1 max_threads=151 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337768 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x9027508 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 = 0xb43b938c thread_stack 0x30000 /home/openxs/dbs/5.1/libexec/mysqld(my_print_stacktrace+0x26)[0x85ff9ba] /home/openxs/dbs/5.1/libexec/mysqld(handle_segfault+0x2b9)[0x827c4e2] [0x353400] /lib/tls/i686/cmov/libc.so.6(abort+0x182)[0x13da82] /lib/tls/i686/cmov/libc.so.6(__assert_fail+0xf8)[0x133718] /home/openxs/dbs/5.1/libexec/mysqld(my_seek+0x103)[0x85dd50f] /home/openxs/dbs/5.1/libexec/mysqld(azrewind+0xfb)[0x84ab814] /home/openxs/dbs/5.1/libexec/mysqld(_ZN10ha_archive16read_data_headerEP11azio_stream+0x55)[0x84a56dd] /home/openxs/dbs/5.1/libexec/mysqld(_ZN10ha_archive5checkEP3THDP15st_ha_check_opt+0x12e)[0x84a9922] /home/openxs/dbs/5.1/libexec/mysqld(_ZN7handler8ha_checkEP3THDP15st_ha_check_opt+0xca)[0x83c48f2] /home/openxs/dbs/5.1/libexec/mysqld[0x83cb4f1] /home/openxs/dbs/5.1/libexec/mysqld(_ZN12ha_partition21handle_opt_partitionsEP3THDP15st_ha_check_optj+0x2cc)[0x83cbacc] /home/openxs/dbs/5.1/libexec/mysqld(_ZN12ha_partition5checkEP3THDP15st_ha_check_opt+0x97)[0x83cb355] /home/openxs/dbs/5.1/libexec/mysqld(_ZN7handler8ha_checkEP3THDP15st_ha_check_opt+0xca)[0x83c48f2] /home/openxs/dbs/5.1/libexec/mysqld[0x83ee1f1] /home/openxs/dbs/5.1/libexec/mysqld(_Z17mysql_check_tableP3THDP10TABLE_LISTP15st_ha_check_opt+0xe0)[0x83f09bc] /home/openxs/dbs/5.1/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x2d5e)[0x8290ea1] /home/openxs/dbs/5.1/libexec/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x265)[0x829a683] /home/openxs/dbs/5.1/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xc9a)[0x828c3c5] /home/openxs/dbs/5.1/libexec/mysqld(_Z10do_commandP3THD+0x26c)[0x828b421] /home/openxs/dbs/5.1/libexec/mysqld(handle_one_connection+0x159)[0x82895b4] /lib/tls/i686/cmov/libpthread.so.0(+0x596e)[0xd6896e] /lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0x1dda4e] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x904ee28): CHECK TABLE `4test_com` ...
[16 Jun 2011 19:17]
Paul DuBois
Noted in 5.1.58, 5.5.14 changelogs. Running mysqlcheck or CHECK TABLE on a corrupted table could cause a server crash.