[MDEV-329] MariaDB 5.5 does not use fdatasync() Created: 2012-06-08 Updated: 2012-06-08 Resolved: 2012-06-08 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.24 |
| Fix Version/s: | 5.5.25 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Kristian Nielsen | Assignee: | Kristian Nielsen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
I discovered a serious problem in 5.5 related to fsync (5.3 and below appears By default, we do not run any fsync at all. This is because the This problem was introduced here: revid:sergii@pisem.net-20111212225840-8aotf02a1alw1gta
The option was renamed and the meaning was reversed - but the default was left We need to fix this ASAP, as it causes data loss / silent corruption when the There is an additional problem that even with --debug-no-sync=0, we are using Work-around: pass --debug-no-sync=0 in config or on command line (but this will not fix fdatasync() performance problem). |
| Comments |
| Comment by Kristian Nielsen [ 2012-06-08 ] |
|
This patch seems to fix it: === modified file 'config.h.cmake' === modified file 'sql/mysqld.cc' , |
| Comment by Kristian Nielsen [ 2012-06-08 ] |
|
Pushed to lp:maria/5.5 |