On Jul 23, 2005, at 10:14 AM, Ware Adams wrote:
Has your mysql crashed or have your restarted the machine without
first shutting down mysql manually? We only saw this error when
mysql was not shut down normally. You can look in your .err file
which should be in your data directory. Every mysql sartup
sequence should be preceded by a line saying "mysqld ended." If
not it's crashing and that's the issue to address.
Nope... nothing like that... just lots of:
[ERROR] Got error 127 when reading table
No crashes at all.
2.) Try Innodb
This is a MyISAM error, but if mysqld is crashing or being shutdown
abnormally InnoDB too will have to go through a crash recovery at
startup (it's just automatic, but you'll see it in the .err file).
so the repair is manual on MyISAM and auto on start-up for Innodb?
I am also wondering about back-ups. The docs seem to indicate
that you can still run mysqldump... but how does this effect
restoring. In my case I can afford to shutdown the server in the
wee hours of the morning and back-up the data dir manually.
1) Shut down and manually copy, but make sure you get all the
InnoDB parts...data files and transaction logs. One is pretty much
useless without the other.
2) mysqldump, look at the options. This with InnoDB is pretty
nice b/c you can use --single-transaction and get a point in time
copy of the table without disrupting other users. In particular
the comments on the mysql documentation page for mysqldump detail a
good set of flags for InnoDB.
3) The (non-free) ibbackup which takes a backup while running
without disturbing users
Im my situation I'm ok with shutting everyone out (via PHP which the
only access to the db) and running either type of back-up.
So if I read you correctly mysqldump locks every one out and dumps.
But with Innodb you can add '--single-transaction' and the dump the
data at that point in time which users continue to work with the
database?
I don't think there's any fundamental issue with MySQL (either
myisam or innodb) on OS X, but I do think that MySQL is something
that doesn't do well when run only through Apple's front end. It
has two many options, configuration details, etc... if you are
doing anything more than a few small tables. Plus, if you are
relying on it all you'll want to be able to take advantage of bug
fixes faster than Apple's MySQL updates allow you too.
Fortunately, it's easy enough to download the mysql binary and use/
configure it independently. We've had quite good luck with MySQL
on OS X with a pretty big install, but there are a lot of details
to learn so it can seem tough to work out at times.
Well Apple does not really have a front end for MySQL at all. I've
gone away from Apple's updates and install my own version from the
source packages provided by MySQL.
Dan T
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
