Operating system errors if innobase_atomic_writes are used on separate undo files that do not exists
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Invalid
|
Undecided
|
Unassigned | ||
5.6 |
Fix Released
|
Medium
|
Laurynas Biveinis |
Bug Description
2013-11-27 11:48:25 7f3e057db720 InnoDB: Operating system error number 9 in a file operation.
InnoDB: Error number 9 means 'Bad file descriptor'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://
2013-11-27 11:48:25 48933 [ERROR] InnoDB: File ./undo001: 'ioctl' returned OS error 109.
Suggested fix:
--- os0file.cc 2013-10-22 10:42:41.000000000 +0300
+++ os0file.cc 2013-11-27 20:56:19.111828166 +0200
@@ -1824,7 +1824,11 @@
}
#endif /* USE_FILE_LOCK */
+ /* In 5.6 we could have separate undo files, but we could
+ come here with bad file descriptor if separate undo
+ file does not exists. */
if (srv_use_
+ && file != -1
&& !os_file_
*success = FALSE;
Related branches
- Stewart Smith (community): Approve
- Registry Administrators: Pending requested
-
Diff: 12 lines (+1/-1)1 file modifiedPercona-Server/storage/innobase/os/os0file.cc (+1/-1)
affects: | percona-xtrabackup → percona-xtradb |
affects: | percona-xtradb → percona-server |
tags: | added: contribution low-hanging-fruit xtradb |
Thanks Jan, we have merged the fix.