Details
Critical
Description
When starting MariaDB 10.0.10 with xtradb or ha_innodb.so, it seems the following configuration options do not work as expected:
innodb_data_home_dir= innodb_data_file_path=/dev/xvde1:3Gnewraw
With MySQL 5.6.17, the error log reports:
[Note] InnoDB: The first specified data file /dev/xvde1 did not exist: a new database to be created! [Note] InnoDB: Setting file /dev/xvde1 size to 3072 MB [Note] InnoDB: Database physically writes the file full
However in MariaDB 10, the error log reports:
[ERROR] InnoDB: '/dev/xvde1' not a regular file. [ERROR] InnoDB: The system tablespace must be writable! [ERROR] Plugin 'InnoDB' init function returned error. [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Gliffy Diagrams
Attachments
Issue Links
- is duplicated by
-
MDEV-6136 RAW storage can't be accessed / initalized
-
- Closed
-
- links to
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
10.0.11 has XtraDB and InnoDB 5.6.17, so this should be fixed in 10.0.11
I have the same problem with 10.0.15-MariaDB (debian repo package).
I wanted to test upgrade from 5.5 to 10.0 so created vm with 5.5.33a version and raw data:
innodb_data_home_dir=
innodb_data_file_path=/dev/raw/raw1:14Graw
/dev/raw/raw1 is created with raw command to point to lvm, read and writeable for everyone and this is worked on 5.5.
root@mysql-test-02:/etc/mysql/conf.d# ls -la /dev/raw/raw1
crwxrwxrwx 1 mysql root 162, 1 Jan 16 19:23 /dev/raw/raw1
root@mysql-test-02:/etc/mysql/conf.d# raw -qa
/dev/raw/raw1: bound to major 253, minor 0
After that change 5.5 mariadb debian (wheezy) repo to 10.0, upgraded mariadb server and got the same error as above:
Jan 18 18:30:03 mysql-test-02 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Warning] option 'innodb-file-io-threads': signed value 1 adjusted to 4
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: Memory barrier is not used
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: Using Linux native AIO
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: Using CPU crc32 instructions
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: Initializing buffer pool, size = 256.0M
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] InnoDB: Completed initialization of buffer pool
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [ERROR] InnoDB: '/dev/raw/raw1' not a regular file.
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [ERROR] InnoDB: The system tablespace must be writable!
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [Note] Plugin 'FEEDBACK' is disabled.
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [ERROR] Unknown/unsupported storage engine: INNODB
Jan 18 18:30:03 mysql-test-02 mysqld: 150118 18:30:03 [ERROR] Aborting
I am still experiencing this issue, with version 10.0.15, using a ZFS ZVOL as my raw device, on FreeBSD.
My bug reports can be seen here.
https://mariadb.atlassian.net/browse/MDEV-7480
It appears to be the upstream bug http://bugs.mysql.com/bug.php?id=69424. It is claimed to be fixed in 5.6.16, while we have 5.6.15 (InnoDB and XtraDB alike), so it should be fixed in 10.0 with the next InnoDB/XtraDB merge.