LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices



Reply
 
Search this Thread
Old 07-15-2010, 01:25 AM   #16
paulsm4
Guru
 
Registered: Mar 2004
Distribution: SusE 8.2
Posts: 5,863
Blog Entries: 1

Rep: Reputation: Disabled

Glad you got it working. It sounds like the two biggest problems were:

1. Not copying all the right files to the right places on the new system
2. You also needed to delete the mysql logs files

It sounds like the Windows data files were InnoDB files - I probably would have kept everything InnoDB. There are pros and cons both ways. But InnoDB is in many ways "better". And I like the credo "if it ain't broke, don't fix it". As in "If your InnoDB database comes up, leave well enough alone and don't change it"

Here's a good comparison of InnoDB for MyISAM:
http://www.kavoir.com/2009/09/mysql-...-and-cons.html

Here's a good description of "mysql log files" and why they're important:
Quote:
http://www.pythian.com/news/1242/

The unsung heroes of InnoDB are the logfiles. They are what makes InnoDB automatic crash recovery possible.

Database administrators of other DBMS may be familiar with the concept of a “redo” log. When data is changed, affected data pages are changed in the innodb_buffer_pool. Then, the change is written to the redo log, which in MySQL is the InnoDB logfile (ib_logfile0 and ib_logfile1). The pages are marked as “dirty”, and eventually get flushed and written to disk...
Anyway, glad you're up and running. Please feel free to click "Thanks" if JohnVV or I helped. And good luck with your newly built/migrated system!
 
1 members found this post helpful.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 07-15-2010, 05:01 AM   #17
thinktink
LQ Newbie
 
Registered: Jun 2010
Posts: 22

Original Poster
Rep: Reputation: 0
Thank you for your help. Even though the solution I had to use was formulated by me, it contains a lot of bits and pieces of help from here.

I am concerned about running a healthy system so I did read the comparison and description links that were provided. I am, however, also concerned about the future.

As was so very seriously demonstrated to me personally, live production servers will fail, hard even. In this instance it appears that it died at such the wrong time that the crash recovery system inherent in InnoDB actually caused more problems for me than they would have potentially solved.

For me, the fact that this option (innodb_data_home_dir) to move what is seemingly an essential file for the InnoDB engine to a location counter-intuitive of data storage even merely existing is a great cause for concern. What if this happened again on a default installation of MySQL like the one I encountered for Windows? What would happen on a partial/failed update/reinstall of MySQL? What about (possibly forced) migrations!!! Even if future install releases, whether by the MySQL dev. team themselves or distro specific, never again specify a location different than would be expected, the potential for it to all go horribly wrong still exists.

What also concerns me about InnoDB is that in this instance to successfully mount the database onto a new system and ultimately recover the underlying data to a usable state I had to delete files. Although, after reading the suggested articles to understand why, of which is now partial, it still seems a bit backwards to me.

Don't get me wrong, I do ascribe to aforementioned adage of "If it ain't broke, don't fix it", but also do ascribe to the old "Murphy's Law" axiom of "Whatever can go wrong, will go wrong." My first hands-on and deep-in-the-trenches experience with InnoDB goes something like this: "It broke and went very wrong."

After today I have come to the personal conclusion that, no-doubt, InnoDB has probably saved others from some probably very serious crashes, but I surmise that if I had been using MyISAM, this thread would have ultimately been much much shorter, whether either by MyISAM completely failing to retain the database on unexpected hardware failure or by just being plain easier to move to another system.



I am posting this not really to rag on InnoDB because of my one and only bad experience (I acknowledge the implications of that) on recovering a database but rather to inform that my decision is not entirely reactionary and completely uninformed. Ultimately, for me, MyISAM might even be better with regards to phpBB anyway:
http://area51.phpbb.com/phpBB//viewt...hp?f=3&t=28738

Last edited by thinktink; 07-15-2010 at 05:06 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How do I convert text files between Windows(Dos) and Linux? gagraf Linux - Newbie 9 01-27-2010 06:26 AM
Application to convert MySQL files MYD, MYI, FRM to SQL text files ? SethShannon Linux - Newbie 1 09-28-2007 07:03 PM
need to convert text files into mysql database zafar466 Linux - Software 1 08-28-2007 01:53 AM
convert MySQL data from Windows to Linux MaaSTaaR Linux - General 2 01-18-2006 07:49 PM


All times are GMT -5. The time now is 04:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration