this one is from another user, it doesn't have the error itself, i'm waiting for that atm, but if you look through it you see that several times the'res no shutdown between starts, which means it just shut down hard, or something.
but; with innodb there is no recovery procedure started, while with xtradb there is.
From what I see, there is recovery each time after the server didn't shutdown normally, be it innodb or xtradb. Example:
111106 12:44:07 InnoDB: 1.1.8 started; log sequence number 835797051
111106 12:44:08 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.15' socket: '/home/pnunn/.local/share/akonadi/socket-localhost.localdomain/mysql.socket' port: 0 Mageia - MySQL Community Edition (GPL)
--> here the previous instance didn't end properly <--
111106 21:52:14 InnoDB: The InnoDB memory heap is disabled
111106 21:52:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111106 21:52:14 InnoDB: Compressed tables use zlib 1.2.5
111106 21:52:14 InnoDB: Using Linux native AIO
111106 21:52:16 InnoDB: Initializing buffer pool, size = 80.0M
111106 21:52:16 InnoDB: Completed initialization of buffer pool
111106 21:52:17 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
--> recovery <--
111106 21:52:17 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
111106 21:52:23 InnoDB: Waiting for the background threads to start
this one is from another user, it doesn't have the error itself, i'm waiting for that atm, but if you look through it you see that several times the'res no shutdown between starts, which means it just shut down hard, or something.
but; with innodb there is no recovery procedure started, while with xtradb there is.
i'll post the error when i get it