Not the answer you need?
Register and ask your own question!

Unable to use Atomic writes on Percona Server 5.5.31 and 5.5.32

nipunnipun EntrantCurrent User Role Beginner
Unable to use Atomic writes on Percona Server 5.5.31 and 5.5.32
#1
Today, 04:21 PM

I am getting the following error, when i try to start the mysql daemon with atomic writes set to 1



[[email protected] ~]# /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
[[email protected] ~]# 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: http://dev.mysql.com/doc/refman/5.5/...ror-codes.html
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

Tags: None







    #2
    Today, 04:23 PM

    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]

    This discussion has been closed.

    MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
    Copyright ©2005 - 2020 Percona LLC. All rights reserved.