# Unable to use Atomic writes on Percona Server 5.5.31 and 5.5.32 **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [August 5, 2013, 3:51pm UTC](https://forums.percona.com/t/unable-to-use-atomic-writes-on-percona-server-5-5-31-and-5-5-32/2858 "2013-08-05T15:51:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![nipun](https://avatars.discourse-cdn.com/v4/letter/n/85f322/32.png) [@nipun](https://forums.percona.com/u/nipun)\ **Post date:** [August 5, 2013, 3:51pm UTC](https://forums.percona.com/t/unable-to-use-atomic-writes-on-percona-server-5-5-31-and-5-5-32/2858/1 "2013-08-05T15:51:13Z")
I am getting the following error, when i try to start the mysql daemon Any help will be appreciated [root@localhost ~]# /root/Percona-Server-5.5.31-rel30.3-520.Linux.x86\_64/bin/mysqld --user=root --datadir=/mnt/fioa/test --innodb-log\_group\_home\_dir=/mnt/fioa/test --innodb-data-home-dir=/mnt/fioa/test --basedir=/root/Percona-Server-5.5.31-rel30.3-520.Linux.x86\_64 & [1] 9539 [root@localhost ~]# 130805 14:09:14 [Note] Plugin ‘FEDERATED’ is disabled. InnoDB: using atomic writes. 130805 14:09:14 InnoDB: The InnoDB memory heap is disabled 130805 14:09:14 InnoDB: Mutexes and rw\_locks use GCC atomic builtins 130805 14:09:14 InnoDB: Compressed tables use zlib 1.2.3 130805 14:09:14 InnoDB: Using Linux native AIO 130805 14:09:14 InnoDB: Initializing buffer pool, size = 4.0G 130805 14:09:14 InnoDB: Completed initialization of buffer pool 130805 14:09:15 InnoDB: Operating system error number 0 in a file operation. InnoDB: Error number 0 means ‘Success’. InnoDB: Some operating system error numbers are described at InnoDB: [url][http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html[/url]](http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html%5B/url%5D) InnoDB: Error in creating or opening /mnt/fioa/test/ibdata1 130805 14:09:15 InnoDB: Could not open or create data files. 130805 14:09:15 InnoDB: If you tried to add new data files, and it failed here, 130805 14:09:15 InnoDB: you should now edit innodb\_data\_file\_path in my.cnf back 130805 14:09:15 InnoDB: to what it was, and remove the new ibdata files InnoDB created 130805 14:09:15 InnoDB: in this failed attempt. InnoDB only wrote those files full of 130805 14:09:15 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 130805 14:09:15 InnoDB: remove old data files which contain your precious data! 130805 14:09:15 [ERROR] Plugin ‘InnoDB’ init function returned error. 130805 14:09:15 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed. 130805 14:09:15 [ERROR] Unknown/unsupported storage engine: InnoDB 130805 14:09:15 [ERROR] Aborting 130805 14:09:15 [Note] /root/Percona-Server-5.5.31-rel30.3-520.Linux.x86\_64/bin/mysqld: Shutdown complete ---
**Author:** ![nipun](https://avatars.discourse-cdn.com/v4/letter/n/85f322/32.png) [@nipun](https://forums.percona.com/u/nipun)\ **Post date:** [August 5, 2013, 3:53pm UTC](https://forums.percona.com/t/unable-to-use-atomic-writes-on-percona-server-5-5-31-and-5-5-32/2858/2 "2013-08-05T15:53:04Z")
The permissions etc in the datadir are proper, and it works when I disable Atomic writes in the my.cnf file My cnf file looks like this [mysqld] #basedir=/usr/local/mysql user=root #socket=/var/lib/mysql/mysql.sock socket=/tmp/mysql.sock server\_id=1 local\_infile=1 skip-grant-table innodb\_buffer\_pool\_size=4G innodb\_use\_native\_aio=1 innodb\_use\_atomic\_writes=1 innodb\_data\_file\_path=ibdata1:10M:autoextend innodb\_file\_per\_table=1 innodb\_flush\_log\_at\_trx\_commit=1 innodb\_lock\_wait\_timeout = 120 innodb\_doublewrite=0 innodb\_log\_block\_size=512 innodb\_fast\_shutdown=0 innodb\_log\_buffer\_size=256M innodb\_log\_files\_in\_group=2 innodb\_log\_file\_size=4G innodb\_thread\_concurrency=32 innodb\_flush\_method = O\_DIRECT innodb\_write\_io\_threads=16 innodb\_read\_io\_threads=16 innodb\_io\_capacity=20000 innodb\_max\_dirty\_pages\_pct=90 max\_connections=3000 query\_cache\_size=0 skip-name-resolve table\_cache=10000 innodb\_adaptive\_flushing=1 innodb\_adaptive\_flushing\_method=keep\_average innodb\_read\_ahead=0 innodb\_flush\_neighbor\_pages=0 innodb\_file\_format=barracuda [mysql] local-infile=1 [client] ---
**Author:** ![niljoshi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/niljoshi/32/16889_2.png) [@niljoshi](https://forums.percona.com/u/niljoshi)\ **Post date:** [August 6, 2013, 11:24pm UTC](https://forums.percona.com/t/unable-to-use-atomic-writes-on-percona-server-5-5-31-and-5-5-32/2858/3 "2013-08-06T23:24:46Z")
Hi, innodb\_use\_atomic\_writes is generally used for Fusion I/O / DirectFS specific options. Are you using any of them? Can you provide some more information like which device model and firmware version you are using? This is implemented in 5.5.31-30 with beta quality so there might be possible that it’s a bug OR there are limited number of devices are supported. Thanks. ---
**Author:** ![nipun](https://avatars.discourse-cdn.com/v4/letter/n/85f322/32.png) [@nipun](https://forums.percona.com/u/nipun)\ **Post date:** [August 14, 2013, 3:38pm UTC](https://forums.percona.com/t/unable-to-use-atomic-writes-on-percona-server-5-5-31-and-5-5-32/2858/4 "2013-08-14T15:38:34Z")
Hi I am using Direct FS on an IO Drive Fusion-io ioDrive2 365GB, Product Number:F00-001-365G-CS-0001, SN:1249D15F2, FIO SN:1249D15F2 Firmware v7.2.5, rev 110646 Public. regards Nipun ---
**Author:** ![niljoshi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/niljoshi/32/16889_2.png) [@niljoshi](https://forums.percona.com/u/niljoshi)\ **Post date:** [August 19, 2013, 10:13pm UTC](https://forums.percona.com/t/unable-to-use-atomic-writes-on-percona-server-5-5-31-and-5-5-32/2858/5 "2013-08-19T22:13:33Z")
Because it’s specific to hardware & uses relatively new api, can we collect system call trace and check?: strace -o strace.log -ff /etc/init.d/mysql start it’s a new feature and could have some permissions/resource allocation bugs without correct error message. Regards, ---
**Author:** ![Raghavendra\_Prabhu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/raghavendra_prabhu/32/16891_2.png) [@Raghavendra\_Prabhu](https://forums.percona.com/u/Raghavendra_Prabhu)\ **Post date:** [August 29, 2013, 5:41am UTC](https://forums.percona.com/t/unable-to-use-atomic-writes-on-percona-server-5-5-31-and-5-5-32/2858/6 "2013-08-29T05:41:19Z")
It is due to [url][https://bugs.launchpad.net/percona-server/+bug/1214735[/url]](https://bugs.launchpad.net/percona-server/+bug/1214735%5B/url%5D). Upgrade to latest Percona Server to fix this.