Hot answers tagged crash
I was able to repro on 2008 R1 SP3 10.00.5512 but installing the latest CU (14) fixed it. Reviewing the bugs fixed in the intervening versions it looks as though you need to upgrade to a build that includes the following fix. Access violation when you run a query that contains many constant values in an IN clause in SQL Server 2008 or in SQL Server 2012 ...
No, rollbacks cannot be done in the background. Both that and the double write checks have to be done before accepting connections again (meaning that if you kill it, you will have to start again on restart). REDO process, however, can and is done in the background. What you can do is kill mysql (again) and restart it skipping that step: /etc/init.d/mysqld ...
I just had the same problem, this was fixed by issuing a command, assuming mysql data dir is on /var/lib/mysql/mysql myisamchk -q -r /var/lib/mysql/mysql/proc Source : http://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html
I take it you are using REPAIR TABLE by hand. I also take it your are doing an automatic table repair for MyISAM. (You have to remove or comment out the option of my.cnf to disable automatic MyISAM table repair). You can actually repair the table without using MySQL but mysqld cannot be accessing it. How? You have to use the offline utility myisamchk ...
Only top voted, non community-wiki answers of a minimum length are eligible