Comment 1 for bug 692211

Revision history for this message
Alexey Kopytov (akopytov) wrote :

Baron,

I cannot repeat the crash. This is what I get after starting with --innodb_auto_lru_dump=5 and no ib_lru_dump in the data dir:

$ ./mysqld --innodb_auto_lru_dump=5
101221 0:58:56 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/var/ is case insensitive
101221 0:58:56 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use InnoDB's own implementation
InnoDB: Compressed tables use zlib 1.2.5
101221 0:58:56 InnoDB: highest supported file format is Barracuda.
101221 0:58:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
 InnoDB: cannot open ib_lru_dump
101221 0:58:56 Percona XtraDB (http://www.percona.com) 1.0.13-12.4 started; log sequence number 527792833
101221 0:58:56 [Note] Event Scheduler: Loaded 0 events
101221 0:58:56 [Note] ./mysqld: ready for connections.
Version: '5.1.53-debug' socket: '/tmp/mysql.sock' port: 3306 Source distribution

Unfortunately, stack traces in the error log are useless for plugins, as addresses are not resolved. Can you run mysqld under gdb and get a gdb stack trace for the crash?