nr: #1 dodano: 2017-01-03 13:01
Actually, the explanation is added in the documentation you linked in the paragraph following
O_DIRECT option's description (highlighting is mine):
O_DIRECT_NO_FSYNC: InnoDB uses O_DIRECT during flushing I/O, but skips the fsync() system call afterward. This setting is suitable for some types of file systems but not others. For example, it is not suitable for XFS. If you are not sure whether the file system you use requires an fsync(), for example to preserve all file metadata, use O_DIRECT instead. This option was introduced in MySQL 5.6.7 (Bug #11754304, Bug #45892).
MySQL bug #45892 contains additional information:
Some testing by Domas has shown that some filesystems (XFS) do not sync metadata without the fsync. If the metadata would change, then you need to still use fsync (or O_SYNC for file open).
For example, if a file grows while O_DIRECT is enabled it will still
write to the new part of the file, however since the metadata doesn't
reflect the new size of the file the tail portion can be lost in the
event of a crash.
Continue to use fsync when important metadata changes or use O_SYNC in
addition to O_DIRECT.
To sum it up: not using fsync() with certain file systems would cause MySQL to fail. However, MySQL offers the option from v5.6.7 to configure MySQL (well, innodb) tailored to your own OS' capabilities in this aspect by adding