MySQL Bugs: #71665: Missing INNODB STATUS OUTPUT if the tmp is full during startup

Bug #71665	Missing INNODB STATUS OUTPUT if the tmp is full during startup
Submitted:	11 Feb 2014 8:50	Modified:	17 Feb 2014 9:04
Reporter:	Miguel Angel Nieto	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.5, 5.5.36	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
If you start a MySQL instance with the /tmp partition full it doesn't fail. But that means that InnoDB's temporary files are not created and things like SHOW ENGINE INNODB STATUS\G don't work anymore. A restart of MySQL is needed. There is no warning or error in the logs.

How to repeat:
Configure a new tmp:

tmpdir=/tmp/kk

fill it with data:

/dev/loop0                      1003     1003         0 100% /kk

Start MySQL.

mysql> show engine innodb status\G
*************************** 1. row ***************************
  Type: InnoDB
  Name:
Status:

Suggested fix:
If for some reason a temporary file can't be created we should stop the startup process. Also, I have only checked with full disk partition. Don't know if this can be triggered with some other storage problems like permissions for example.

Hello Miguel,

Thank you for the bug report.
Verified as described.

Thanks,
Umesh