Error: Cannot create '/databasesib_modified_log_1_0.xdb'

Bug #1181887 reported by Ryan Gordon on 2013-05-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to
Fix Released
Laurynas Biveinis
Fix Released
Laurynas Biveinis
Fix Released
Laurynas Biveinis
Fix Released
Laurynas Biveinis

Bug Description

Running Percona Server 5.5.30-30.2 on Solaris 11 (SunOS 5.11) with the following relevant configuration options:

innodb_data_home_dir = /databases
innodb_log_group_home_dir = /databases
innodb_track_changed_pages = 1

On bootup MySQL starts normally but then fails because it tries to create the file in the wrong place.

130520 1:00:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130520 1:00:02 InnoDB: Compressed tables use zlib 1.2.3
130520 1:00:02 InnoDB: Initializing buffer pool, size = 12.0G
130520 1:00:06 InnoDB: Completed initialization of buffer pool
130520 1:00:06 InnoDB: highest supported file format is Barracuda.
130520 1:00:07 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: Cannot create '/databasesib_modified_log_1_0.xdb'

Changing the variable to innodb_data_home_dir = /databases/ seems to fix the issue. This does not seem like standard behavior because the rest of MySQL has and continues to work without needing the appended slash. The file should be saved to '/databases/ib_modified_log_1_0.xdb' without needing to change the innodb_data_home_dir setting


Related branches

Thank you for the bug report.

tags: added: bitmap
tags: added: xtradb

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers