Hi,
Or is there any possibility to reproduce this table crash after
repairing the table once? This would clearly indicate a bug in MySQL.
I'll try, but since it's a 'production' system I can't experiment too much.
See http://ftp.osuosl.org/pub/mysql/doc/refman/5.0/en/system.html for
an
Hello Olaf
On 2005-12-17 Olaf van der Spek wrote:
See http://ftp.osuosl.org/pub/mysql/doc/refman/5.0/en/system.html for
an explanation of this option.
It says:
The only case in which you cannot use --skip-external-locking is ... if
you run myisamchk to check (not repair) a table
Package: mysql-server-5.0
Version: 5.0.16-1
Severity: important
Hi,
After a restart I got 'Incorrect key file for table' errors and 'Table '...' is
marked as crashed and should be repaired' errors.
From syslog:
Dec 16 19:25:09 b mysqld[19851]: 051216 18:25:09 [Note] /usr/sbin/mysqld:
Normal
severity 343639 normal
tag 343639 + moreinfo upstream
thanks
Hello Olaf
On 2005-12-16 Olaf van der Spek wrote:
After a restart I got 'Incorrect key file for table' errors and 'Table '...'
is marked as crashed and should be repaired' errors.
I've got these kind of errors a couple of times in
4 matches
Mail list logo
