Percona server corrupt database after full disk

[Fabian Niepelt]

Hello,

we've had two instances lately where the disk the database was stored on became full. In both cases, the database ultimately got corrupted and percona crashes with a segmentation fault on start if not starting with innodb_force_recovery=6.
I attached a file with relevant log entries.

Commandline: sudo -u mysql -- /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --open-files-limit=65535 --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306 --log-syslog=0
Tool version: 5.7.17-11-1.xenial
MySQL Version of all servers involved: 5.7.17-11-1.xenial
Output from the tool including STDERR: See attachment
Input files: We are forbidden to share the database files.
OS: Ubunutu 16.04.2

The mysql documentation states, that it should be able to handle this situation gracefully https://dev.mysql.com/doc/refman/5.7/en/full-disk.html.

Greetings
Fabian

[Miguel Angel Nieto (miguelangelnieto)]

Hello,

Thanks for your report, but you should create it in the Percona Server launchpad project. This one is for Percona Toolkit.

https://launchpad.net/percona-server

Thanks!

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1429