MySQL Bugs: #65208: InnoDB fails to start if datadir located on btrfs partition

Bug #65208	InnoDB fails to start if datadir located on btrfs partition
Submitted:	5 May 2012 4:39	Modified:	8 Jun 2012 19:23
Reporter:	Valentine Gostev	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB Plugin storage engine	Severity:	S2 (Serious)
Version:	5.5	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	btrfs, innodb

Description:
mysqld with innodb enabled fails to start against datadir located on btrfs partition

Server log is:
120505  7:40:53 [Note] Flashcache bypass: disabled
120505  7:40:53 [Note] Flashcache setup error is : open flash device failed

120505  7:40:53 [Note] Plugin 'FEDERATED' is disabled.
120505  7:40:53 InnoDB: The InnoDB memory heap is disabled
120505  7:40:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120505  7:40:53 InnoDB: Compressed tables use zlib 1.2.3
120505  7:40:53 InnoDB: Using Linux native AIO
120505  7:40:53 InnoDB: Initializing buffer pool, size = 32.0M
120505  7:40:53 InnoDB: Completed initialization of buffer pool
120505  7:40:53 InnoDB: highest supported file format is Barracuda.
120505  7:40:53  InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'aio write'.
InnoDB: Cannot continue operation.

Server log is:
...
120505  7:40:54 [Note] Plugin 'FEDERATED' is disabled.
120505  7:40:54 InnoDB: The InnoDB memory heap is disabled
120505  7:40:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120505  7:40:54 InnoDB: Compressed tables use zlib 1.2.3
120505  7:40:54 InnoDB: Using Linux native AIO
120505  7:40:54 InnoDB: Initializing buffer pool, size = 32.0M
120505  7:40:54 InnoDB: Completed initialization of buffer pool
120505  7:40:54 InnoDB: highest supported file format is Barracuda.
120505  7:40:54  InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'aio write'.
InnoDB: Cannot continue operation.

Looks to be old issue http://kerneltrap.org/mailarchive/linux-btrfs/2010/10/6/6885658

but searching for btrfs lead to nothing here.

How to repeat:
Start mysqld+innodb on btrfs partition

does adding "innodb_use_native_aio=0" to my.cnf make it start up ?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".