Bug #72287 | mysqld crash during REORGANIZE PARTITION | ||
---|---|---|---|
Submitted: | 9 Apr 2014 9:02 | Modified: | 16 May 2018 15:17 |
Reporter: | Conor Murphy | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Partitions | Severity: | S1 (Critical) |
Version: | 5.6.16-log | OS: | Solaris (s10x_u10wos_17b) |
Assigned to: | CPU Architecture: | Any |
[9 Apr 2014 9:02]
Conor Murphy
[9 Apr 2014 10:39]
MySQL Verification Team
What is the table structure? SHOW CREATE TABLE hires_disk_stat \G
[9 Apr 2014 10:41]
Conor Murphy
mysql> SHOW CREATE TABLE hires_disk_stat\G *************************** 1. row *************************** Table: hires_disk_stat Create Table: CREATE TABLE `hires_disk_stat` ( `time` datetime NOT NULL, `diskid` mediumint(8) unsigned NOT NULL, `busy` tinyint(3) unsigned NOT NULL, `rws` int(10) unsigned NOT NULL, `blks` int(10) unsigned NOT NULL, `avque` decimal(4,1) unsigned NOT NULL, `avwait` decimal(5,1) unsigned NOT NULL, `avserv` decimal(5,1) unsigned NOT NULL, KEY `myidx` (`time`,`diskid`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 /*!50100 PARTITION BY RANGE ( TO_DAYS(time)) (PARTITION P20070101 VALUES LESS THAN (733042) ENGINE = MyISAM, PARTITION P20080101 VALUES LESS THAN (733407) ENGINE = MyISAM, PARTITION P20090101 VALUES LESS THAN (733773) ENGINE = MyISAM, PARTITION P20100101 VALUES LESS THAN (734138) ENGINE = MyISAM, PARTITION P20110101 VALUES LESS THAN (734503) ENGINE = MyISAM, PARTITION P20120101 VALUES LESS THAN (734868) ENGINE = MyISAM, PARTITION P20130101 VALUES LESS THAN (735234) ENGINE = MyISAM, PARTITION P20130401 VALUES LESS THAN (735324) ENGINE = MyISAM, PARTITION P20130501 VALUES LESS THAN (735354) ENGINE = MyISAM, PARTITION P20130601 VALUES LESS THAN (735385) ENGINE = MyISAM, PARTITION P20130701 VALUES LESS THAN (735415) ENGINE = MyISAM, PARTITION P20130801 VALUES LESS THAN (735446) ENGINE = MyISAM, PARTITION P20130901 VALUES LESS THAN (735477) ENGINE = MyISAM, PARTITION P20131001 VALUES LESS THAN (735507) ENGINE = MyISAM, PARTITION P20131101 VALUES LESS THAN (735538) ENGINE = MyISAM, PARTITION P20131201 VALUES LESS THAN (735568) ENGINE = MyISAM, PARTITION P20140101 VALUES LESS THAN (735599) ENGINE = MyISAM, PARTITION P20140201 VALUES LESS THAN (735630) ENGINE = MyISAM, PARTITION P20140301 VALUES LESS THAN (735658) ENGINE = MyISAM, PARTITION P20140401 VALUES LESS THAN (735689) ENGINE = MyISAM, PARTITION P20140402 VALUES LESS THAN (735690) ENGINE = MyISAM, PARTITION P20140403 VALUES LESS THAN (735691) ENGINE = MyISAM, PARTITION P20140404 VALUES LESS THAN (735692) ENGINE = MyISAM, PARTITION P20140405 VALUES LESS THAN (735693) ENGINE = MyISAM, PARTITION P20140406 VALUES LESS THAN (735694) ENGINE = MyISAM, PARTITION P20140407 VALUES LESS THAN (735695) ENGINE = MyISAM, PARTITION P20140408 VALUES LESS THAN (735696) ENGINE = MyISAM, PARTITION P20140409 VALUES LESS THAN (735697) ENGINE = MyISAM, PARTITION PMAXVALUE VALUES LESS THAN MAXVALUE ENGINE = MyISAM) */ 1 row in set (0.03 sec) mysql>
[9 Apr 2014 10:43]
MySQL Verification Team
/opt/mysql/mysql/bin/mysqld: Incorrect key file for table './statsdb/hires_disk_stat#P#P20130501#TMP#.MYI'; try to repair it Also make sure enough disk space is available...
[9 Apr 2014 10:52]
Conor Murphy
Should be enough disk space, I haven't seen any messages about the file system being full $ df -h /data/db Filesystem size used avail capacity Mounted on datapool/data/db 3.9T 1.4T 405G 79% /data/db $ The partitions being merged have ~ 10.5GB (MYD+MYI) $ ls -lth hires_disk_stat* | egrep 'P20130401|P20130501' -rw-rw---- 1 mysql mysql 1.0G Mar 11 15:14 hires_disk_stat#P#P20130501.MYI -rw-rw---- 1 mysql mysql 3.2G Mar 11 15:14 hires_disk_stat#P#P20130401.MYI -rw-rw---- 1 mysql mysql 4.5G Mar 8 06:48 hires_disk_stat#P#P20130401.MYD -rw-rw---- 1 mysql mysql 1.8G Feb 11 03:42 hires_disk_stat#P#P20130501.MYD
[16 Apr 2018 15:17]
MySQL Verification Team
It was done the repair table and tested with new releases. Thanks.
[17 May 2018 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".