Hello,
I did something dumb: ran myisamchk while mysqld was up and running and, being
on a linux system, I run the deamon with --skip-locking. This is what I guess made one
of my tables appear to be empty. According to the manual if you run myisamchk while
someone else is doing an update on the table, you corrupt it.
But there are two things that made me think twice:
1) I afterwards shutdown the server and re-ran myisamchk with --information
--check (and later with --extend-check) and it says that the table has 32 records
(which are excactly what it's supposed to have) and that everything is just fine
2) the table that lost its records, isn't one of the tables that get updated
at all :-( It is totally static. So even if running myisamchk with mysqld running is a
bad thing to do, still I wouldn't expect THIS table to get corrupted.
3)I had a backup (bit of wisdom in midst of the stupidity) and I recovered the
data. I notices that the data file .MYD was half the size that in my backup, and the
index MYI and .frm was just fine (which explains why myisamchk thought everything was
just fine)
Any ideas how I could have brought back the 32 recs that myisamchk says are there, but
I cannot see?
Is there some utility to check the .MYD file's integrity?
Also in the manual it says that --skip-locking is used due to locking deficiencies of
the OS locking of some linux systems. Can someone define which these linux systems
are? I am running on 2.2.13 (slackware7), is it safe to remove the --skip-locking?
regards,
thalis
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
