Bug #70298 | [ERROR] InnoDB: Failed to set O_DIRECT on file | ||
---|---|---|---|
Submitted: | 11 Sep 2013 12:12 | Modified: | 27 Sep 2013 13:01 |
Reporter: | Arnaud Adant | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.6.12 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[11 Sep 2013 12:12]
Arnaud Adant
[27 Sep 2013 13:01]
Erlend Dahl
[25 Sep 2013 5:05] Daniel T Price Noted in 5.6.15 changelog. Setting the "O_DIRECT" flag on a file on "tmpfs" on some operating systems would result in an error printed to the error log. Creating multiple temporary tables on "tmpfs" would cause the error to be printed repeatedly. The error message has been changed to a warning that is only printed once when running "CREATE TABLE" multiple times.
[4 Dec 2013 11:42]
Laurynas Biveinis
5.6$ bzr log -r 5469 ------------------------------------------------------------ revno: 5469 committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.6 timestamp: Mon 2013-09-23 21:44:36 +0530 message: Bug #17441867 [ERROR] INNODB: FAILED TO SET O_DIRECT ON FILE PROBLEM ------- Setting the O_DIRECT flag on file on tmpfs fails and error messages are printed in error logs. The customer was creating lot of temporary tables in tmpfs and because of which error log was flooded with these error messages. We however ignore these errors and continue to create the tables.These error messages were causing problem with the their monitoring system. FIX --- The fix is to downgrade the error with a warning and printing this warning only once in the error log.
[27 May 2014 6:59]
Roel Van de Paar
Agree on downgrade to warning. And, if there would ever be talk about dropping the warning altogether, I would disagree - this warning is handy for QA to establish what happened exactly and thereby to ensure 100% reproducible testcases.