Created
January 9, 2011 13:39
-
-
Save josip/771691 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| =INFO REPORT==== 9-Jan-2011::13:38:43 === | |
| Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_hook) host starting (<0.156.0>) | |
| InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 110109 13:38:44 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! | |
| 110109 13:38:44 InnoDB: Database was not shut down normally! | |
| InnoDB: Starting crash recovery. | |
| InnoDB: Reading tablespace information from the .ibd files... | |
| InnoDB: Error: trying to add tablespace 263 of name '/var/lib/riak/innodb/innokeystore/bus_stops_1050454301831586472458898473514828420377701515264.ibd' | |
| InnoDB: to the tablespace memory cache, but tablespace | |
| InnoDB: 263 of name '/var/lib/riak/innodb/innokeystore/__riak_client_test___1118962191081472546749696200048404186924073353216.ibd' already exists in the tablespace | |
| InnoDB: memory cache! | |
| Erlang has closed | |
| /usr/lib/riak/lib/os_mon-2.2.5/priv/bin/memsup: Erlang has closed. |
Cool. I figured it out based on mailing list support. I should write a blog post about it so I don't forget how to solve it. :P
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I remember correctly, I solved it before someone on IRC suggested anything - I just deleted the .ibd file in question (the latter one), haven't had any problems after that. I presume Tiak/InnoDB haven't had time to delete the old file before it was forcefully closed.