CURRENT_TEST: main.1st 2013-04-08 12:26:17 0 [Warning] The syntax '--master-retry-count' is deprecated and will be removed in a future release. Please use 'CHANGE MASTER TO master_retry_count = ' instead. 2013-04-08 12:26:17 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2013-04-08 12:26:17 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4162) 2013-04-08 12:26:17 9375 [Note] Plugin 'FEDERATED' is disabled. 2013-04-08 12:26:17 9375 [Note] InnoDB: The InnoDB memory heap is disabled 2013-04-08 12:26:17 9375 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2013-04-08 12:26:17 9375 [Note] InnoDB: Compressed tables use zlib 1.2.3 2013-04-08 12:26:17 9375 [Note] InnoDB: CPU does not support crc32 instructions 2013-04-08 12:26:17 9375 [Note] InnoDB: Using Linux native AIO 2013-04-08 12:26:17 9375 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2013-04-08 12:26:17 9375 [Note] InnoDB: Completed initialization of buffer pool 2013-04-08 12:26:17 9375 [Note] InnoDB: Highest supported file format is Barracuda. 2013-04-08 12:26:17 9375 [Note] InnoDB: 128 rollback segment(s) are active. 2013-04-08 12:26:17 9375 [Note] InnoDB: Waiting for purge to start 2013-04-08 12:26:17 9375 [Note] InnoDB: 1.2.10 started; log sequence number 1625977 2013-04-08 12:26:17 9375 [Warning] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld: unknown option '--loose-skip-ndbcluster' 2013-04-08 12:26:17 9375 [Warning] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld: unknown option '--loose-debug-assert-if-crashed-table' 2013-04-08 12:26:17 9375 [Warning] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld: unknown option '--loose-debug-assert-on-error' 2013-04-08 12:26:17 9375 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 5dda344d-a02e-11e2-920a-0017f20c07dc. 2013-04-08 12:26:17 9375 [Note] Server hostname (bind-address): '*'; port: 13100 2013-04-08 12:26:17 9375 [Note] IPv6 is available. 2013-04-08 12:26:17 9375 [Note] - '::' resolves to '::'; 2013-04-08 12:26:17 9375 [Note] Server socket created on IP: '::'. 2013-04-08 12:26:17 9375 [Warning] 'user' entry 'root@macpro2.percona.com' ignored in --skip-name-resolve mode. 2013-04-08 12:26:17 9375 [Warning] 'proxies_priv' entry '@ root@macpro2.percona.com' ignored in --skip-name-resolve mode. 2013-04-08 12:26:17 9375 [Note] Event Scheduler: Loaded 0 events 2013-04-08 12:26:17 9375 [Note] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld: ready for connections. Version: '5.6.10-alpha60.2-log' socket: '/ssd/921647/current1_6/tmp/master.sock' port: 13100 Percona Server with XtraDB (GPL), Release alpha60.2, Revision 314 2013-04-08 19:56:24 7f6b9fe26700 InnoDB: Error: Write to file ./query09542/#sql-ib9997.ibd failed at offset 2097152. InnoDB: 1048576 bytes should have been written, only 487424 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:56:48 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 49152 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:57:02 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 byteInnoDB: Error number 28 means 'No space left on device'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:58:08 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 94208 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:58:12 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 802816 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:58:14 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 1003520 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:58:15 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 913408 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:58:16 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 249856 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:58:17 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 421888 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:58:19 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 663552 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:58:21 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 53248 were written. InnoDB: Operating system error InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:19 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 741376 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:21 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 532480 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:23 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 557056 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:24 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 532480 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:25 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 946176 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:26 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 929792 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:27 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 892928 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:27 7f6b9fe26700 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 843776 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system sup InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 999424. InnoDB: 16384 bytes should have been written, only -1 were written. InnoDB: Operating system error number 28. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 28 means 'No space left on device'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:34 7f6b9fda4700 InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 950272. InnoDB: 16384 bytes should have been written, only -1 were written. InnoDB: Operating system error number 28. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 28 means 'No space left on device'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:36 7f6b9fda4700 InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 819200. InnoDB: 16384 bytes should have been written, only 4096 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:37 7f6b9fda4700 InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 1048576. InnoDB: 1048576 bytes should have been written, only 581632 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:37 7f6b9fda4700 InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 1048576. InnoDB: 1048576 bytes should have been written, only 581632 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:37 7f6b9fda4700 InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 278528. InnoDB: 16384 bytes should have been written, only -1 were written. InnoDB: Operating system error number 28. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 28 means 'No space left on device'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:37 7f6b9fda4700 InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 950272. InnoDB: 16384 bytes should have been written, only 4096 were written. InnoDB: Operating system error number 0. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 0 means 'Success'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:38 7f6b9fda4700 InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 1048576. InnoDB: 1048576 bytes should have been written, only 73728 were written. InnoDB: Operati2013-04-08 19:59:38 7f6b9fda4700 InnoDB: Error: Write to file ./query19542/#sql-ib10080.ibd failed at offset 753664. InnoDB: 16384 bytes should have been written, only -1 were written. InnoDB: Operating system error number 28. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 28 means 'No space left on device'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-04-08 19:59:38 7f6b9fda4700 InnoDB: Assertion failure in thread 140100220110592 in file btr0btr.cc line 693 InnoDB: Failing assertion: mach_read_from_4(seg_header + FSEG_HDR_SPACE) == space 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.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 16:59:38 UTC - 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=1048576 read_buffer_size=131072 max_used_connections=33 max_threads=153 thread_count=3 connection_count=3 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61849 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x26b9f10 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 = 7f6b9fda3e18 thread_stack 0x40000 /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(my_print_stacktrace+0x35)[0x8ad525] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(handle_fatal_signal+0x4b4)[0x654a94] /lib64/libpthread.so.0(+0xf500)[0x7f6bbde50500] /lib64/libc.so.6(gsignal+0x35)[0x7f6bbcafc8a5] /lib64/libc.so.6(abort+0x175)[0x7f6bbcafe085] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x9e4a01] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x9e535f] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0xa22bfe] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x9a92c0] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x9aa6e1] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x96b028] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x96b535] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x991a88] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x911fc0] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld[0x915676] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP10TABLE_LISTP10Alter_infojP8st_orderb+0x3474)[0x718934] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x447)[0x7f9ad7] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1dd1)[0x6ca601] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x32f)[0x6cd56f] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1861)[0x6cf311] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(_Z24do_handle_one_connectionP3THD+0xcf)[0x69d5af] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(handle_one_connection+0x47)[0x69d6d7] /ssd/Percona-Server-5.6.8-alpha60.2-314.Linux.x86_64/bin/mysqld(pfs_spawn_thread+0x139)[0x8e4969] /lib64/libpthread.so.0(+0x7851)[0x7f6bbde48851] /lib64/libc.so.6(clone+0x6d)[0x7f6bbcbb211d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f6b3c03fa00): ALTER TABLE query19542 . `t1` DROP COLUMN `c72` Connection ID (thread ID): 2900 Status: NOT_KILLED 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. Writing a core file