Thanks Dave,
I added a .bak to the older file and everything got cleaned up.
Thanks for Googling better than me.. ;)
Jimmy
On Wed, Apr 20, 2011 at 9:43 AM, Dave Barnes wrote:
> I wouldn't delete anything, I would move the file(s) that I though was old
> or not valid. Then re-try a db restart.
I wouldn't delete anything, I would move the file(s) that I though was old
or not valid. Then re-try a db restart.
Remember, I have no actually experience with this type of database, but it
appears to be a simple structure.
See last comment here might help:
http://www.opsview.com/forum/opsview-co
Thanks Dave,
Those files do both exist. Am I right in understanding from that mysql post
that the files would be regenerated from the real data, and that deleting
them won't cause a problem?
Jimmy
On Wed, Apr 20, 2011 at 9:35 AM, Dave Barnes wrote:
> Check out comments by Heikki at bottom:
>
>
Check out comments by Heikki at bottom:
http://bugs.mysql.com/bug.php?id=10863
On Wed, Apr 20, 2011 at 9:27 AM, Dave Barnes wrote:
> not an expert in innodb - guessing based upon other readings... :)
>
> Do both of these files exist?
>
>
> /riak/data/innokeystore/user1019,201103_8906025602485
not an expert in innodb - guessing based upon other readings... :)
Do both of these files exist?
/riak/data/innokeystore/user1019,201103_890602560248518965780370444936484965102833893376.ibd
/riak/data/innokeystore/user6425,201103_388211372416021087647853783690262677096107081728.ibd
On Wed, Apr
I'm having some trouble with InnoDB. One of our nodes crashed, and during
error recovery, I received the following message:
http://pastebin.com/mNF2Tr8D
I've seen a little about this on Google, but not enough to make me
comfortable enough to solve it.
Has anybody else seen this? If so, how should
