Was upgrading today and got this:
Setting up mysql-server-5.5 (5.5.28-0ubuntu0.12.10.1) ... start: Job failed to start invoke-rc.d: initscript mysql, action "start" failed. dpkg: error processing mysql-server-5.5 (--configure): subprocess installed post-installation script returned error exit status 1
yay, so it can’t start for some reason..
#tail -n 20 /var/log/mysql/error.log:
121211 20:37:00 [Note] Plugin 'FEDERATED' is disabled. 121211 20:37:00 InnoDB: The InnoDB memory heap is disabled 121211 20:37:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121211 20:37:00 InnoDB: Compressed tables use zlib 1.2.7 121211 20:37:00 InnoDB: Using Linux native AIO 121211 20:37:00 InnoDB: Initializing buffer pool, size = 128.0M 121211 20:37:00 InnoDB: Completed initialization of buffer pool 121211 20:37:00 InnoDB: highest supported file format is Barracuda. 121211 20:37:00 InnoDB: Operating system error number 22 in a file operation. InnoDB: Error number 22 means 'Invalid argument'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html InnoDB: File name ./ib_logfile0 InnoDB: File operation call: 'aio write'. InnoDB: Cannot continue operation.
Google says aio on tmpfs doesn’t work. I don’t want mysql to store it’s crap on my disk – it is just my desktop db and I don’t need it to be blazing fast and contribute to ssd wear.
Solution in my case is innodb_use_native_aio = 0 in my.cnf