enterprise-support team mailing list archive

[Miguel Angel Nieto <1278772@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: mysql-server
     Importance: Unknown
         Status: Unknown

** Affects: percona-server
     Importance: Undecided
         Status: New


** Tags: i39334

** Bug watch added: MySQL Bug System #71665
   http://bugs.mysql.com/bug.php?id=71665

** Also affects: mysql-server via
   http://bugs.mysql.com/bug.php?id=71665
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1278772

Title:
  Missing INNODB STATUS OUTPUT if the tmp is full during startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1278772/+subscriptions