MySql Import speed(Was mysql version OSX)

Lou Picciano loupicciano at
Tue Dec 21 18:46:03 EST 2010

Mike et al, 

For what it's worth, we have run into this behavior before with MySQL; this may be of use to someone. Underlying issue: a full-to-capacity log file. If your tablespaces are on multiple drives/filesystems (ours are), and your logs are on others (ours are!), one might be forgiven for not immediately recognizing that MySQL had filled its logs! (Yes, of course, here begins a good discussion of logfile rotation/hygiene). 

Not exactly a stopped-working-because-the-database-got-too-big error; it might rather be called (delicately): 'Pilot Error' (!!) 

When we first saw this (and believe me, there won't be a second time!), it was a bit misleading, because MySQL, to its credit, was 'apparently' still running... None of the traditional UNIXy ugliness like core dumps, service dropoffs, etc. were seen. But the DB starting responding to queries inappropriately, and sometimes not at all. Was a bit of a nailbiter. I can now happily say this was 'Long Ago, in a Universe Far, Far Away...' 

Happy Holidays to All, Lou 

----- Original Message ----- 
From: "Mike Matthews" <omnis at> 
To: "OmnisDev List - English" <omnisdev-en at> 
Sent: Tuesday, December 21, 2010 5:54:56 PM 
Subject: Re: MySql Import speed(Was mysql version OSX) 

The big issue here was this BigRedBox, did I mention this before? We don't know jack diddly about it, and even less about the admin passwords, etc. But we took out the HD and then had the data out anyway. 

The problem was that the mail server software services wouldn't start, file sharing services wouldn't start, so now you know. Every day that goes by, the data becomes out of date and more irrelevant. They have all the new email, but no old stuff at all, as it was accessed by webmail. There is no support for this box, unpaid support invoices, a bankrupt company, etc, a whole nasty can of worms. I got the data imported in about 4 hours in the end by turning the log-output=NONE, but interestingly on a Win32 box and MySql v5.1, the import struggled to get anywhere, but my MBP and with v5.58, it did it in about 4 hours. 

I just used the WorkBench and the Import section, seemed simple enough, which suits me, just a pain that I had to update the one file and make the my.cnf file which is just plain stoopid. 

All academic as the customer bit the bullet, paid the old support invoices, and will hopefully get the BigRedBox, that really is the name, and it is Red, back working so that the old historical email can be pulled out. The sql data is very obfuscated when I looked, mostly BLOBs and just pkeys, so impossible to make a valid judgement in a few hours. 

The trip was worth it, as I now understand much more than I did about MySql, which is good, but leaves many questions for later. So no problem with size, just lack of admin info. 

Thanks for the help to all. 


On 21 Dec 2010, at 21:53, CLIFFORD ILKAY wrote: 

> On 12/20/2010 05:40 PM, Mike Matthews wrote: 
>> Thanks Clifford, 
>> All good intel, I'll read up the basic difference between these two 
>> in the morning. Right now, I just want the the data back and so I 
>> can read it, I don't expect to want to add to it. 
>> As I said, the DB came from a turnkey linux system called BigRedBox, 
>> and yes, it was a big red box that did all of your small office 
>> stuff. But now it has gone wrong and the email system won't open the 
>> DB, maybe because it is too big. But they need some of the data 
>> back, etc. 
> I've never encountered a MySQL db that can't be opened because it's too big. What exactly is the problem? "It has gone wrong" isn't very descriptive. :) Systems don't just stop working for no reason. It might be more productive to figure out why it stopped working and get it going. It should be quite feasible for someone who understands Linux to do that. 
> -- 
> Regards, 
> Clifford Ilkay 
> Dinamis 
> 1419-3266 Yonge St. 
> Toronto, ON 
> Canada M4N 3P6 
> <> 
> +1 416-410-3326 
> _____________________________________________________________ 
> Manage your list subscriptions at 

Manage your list subscriptions at 

More information about the omnisdev-en mailing list