i'm also seeing this failure on an attempted mysql upgrade from squeeze to wheezy.
however, unless i'm misunderstanding something, i find i'm not successful in applying the workaround mentioned in http://bugs.debian.org/682232#22 I tried: echo 'innodb_force_recovery = 1' > /etc/mysql/conf.d/fix_682232.conf /etc/init.d/mysql start but i'm still getting a failure to start, and the following messages in the syslog: > Jun 24 12:41:28 tigra mysqld: 130624 12:41:28 [Note] Plugin 'FEDERATED' is > disabled. > Jun 24 12:41:28 tigra mysqld: 130624 12:41:28 InnoDB: The InnoDB memory heap > is disabled > Jun 24 12:41:28 tigra mysqld: 130624 12:41:28 InnoDB: Mutexes and rw_locks > use GCC atomic builtins > Jun 24 12:41:28 tigra mysqld: 130624 12:41:28 InnoDB: Compressed tables use > zlib 1.2.7 > Jun 24 12:41:28 tigra mysqld: 130624 12:41:28 InnoDB: Using Linux native AIO > Jun 24 12:41:29 tigra mysqld: 130624 12:41:29 InnoDB: Initializing buffer > pool, size = 128.0M > Jun 24 12:41:29 tigra mysqld: 130624 12:41:29 InnoDB: Completed > initialization of buffer pool > Jun 24 12:41:29 tigra mysqld: 130624 12:41:29 InnoDB: highest supported file > format is Barracuda. > Jun 24 12:41:29 tigra mysqld: 130624 12:41:29 InnoDB: Error: trying to > access tablespace 1 page no. 2, > Jun 24 12:41:29 tigra mysqld: InnoDB: but the tablespace does not exist or is > just being dropped. > Jun 24 12:41:29 tigra mysqld: 130624 12:41:29 InnoDB: Error: trying to > access tablespace 1 page no. 2, > Jun 24 12:41:29 tigra mysqld: InnoDB: but the tablespace does not exist or is > just being dropped. ... this is on a powerpc system, fwiw, with only one non-system database (and that db has only one active table), and no InnoDB tables in the entire installation. the machine is still in this broken state. I'm happy to provide debugging information if it would be useful. --dkg
signature.asc
Description: OpenPGP digital signature
