Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.5.28
-
Fix Version/s: 5.5.28a
-
Component/s: None
-
Labels:None
-
Environment:windows server 2008 x64,
version 5.5.28-MariaDB-log
version_comment mariadb.org binary distribution
version_compile_machine x86
version_compile_os Win64
Percona XtraDB (http://www.percona.com) 1.1.8-29.0
Description
Hello!
I download mariadb yesterday and get error with innodb options innodb_buffer_pool_restore_at_startup
When i set it, i get in error log next messages :
121030 10:25:40 InnoDB: Operating system error number 183 in a file operation.
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_lru_dump.tmp
InnoDB: File operation call: 'rename'.
In the datadir i see two files: "ib_lru_dump.tmp" and "ib_lru_dump"
I am newby with mariadb, but i have some years expirience of using oracle and percona mysql. And i had never been seen such error: percona xtradb works well with buffer restore, even oracle mysql saves/restores innodb pages clearly.
What is reason of problem? I missed something in cfg file or it's really bug?
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Very much reproducible on Windows 7 x64.
- downloaded mariadb-5.5.28-winx64.zip;
- unpacked;
- cd-ed to the unpacked folder;
- ran
bin\mysqld --innodb_buffer_pool_restore_at_startup=1
It creates ib_lru_dump on startup, and then starts updating ib_lru_dump.tmp complaining every 5 seconds as described above.
The server remains available and, as it seems, functional (can connect and run queries).
All permissions to the datadir are okay (new local datadir).
is it only Win64 issue? not repeatable on Linux?
Sorry, forgot to mention. Not repeatable on Ubuntu 11.10 oneiric x86_64.
Operating system error 183 is ERROR_ALREADY_EXISTS
@Oleg - the reason for this behavior is a real bug. To prevent message flood in the log file, I'd switch off innodb_buffer_pool_restore_at_startup until 5.5.29 release, where it is going to be fixed.
Elena, can you try to verify that? If you don't have Win64 handy, please reassign it to @wlad