MySQL Bugs: #31027: should use O_SYNC on innodb data files for VxFS

Bug #31027	should use O_SYNC on innodb data files for VxFS
Submitted:	14 Sep 2007 9:50	Modified:	13 May 2010 16:04
Reporter:	River Tarnell	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S4 (Feature request)
Version:	5.0.42	OS:	Solaris
Assigned to:	Assigned Account	CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
To enable direct I/O (unbuffered) when using VxFS, the usual method is for the application (InnoDB) to open the file with O_SYNC, and the filesystem to be mounted with the "convosync=direct" option.  InnoDB does not open data files with O_SYNC, only log files, even when innodb_flush_method = O_DIRECT is specified.  Contrary to what the manual says, "convosync=direct" does _not_ help performance in this case.

How to repeat:
N/A

Suggested fix:
Add an additional innodb_flush_method which causes data files as well as log files to be opened with O_SYNC.

Thank you for a reasonable feature request.