Rolf,
Tuesday, September 03, 2002, 1:57:49 AM, you wrote:
RH I'm using MySQL 3.23.51. I have a table which started giving 127 errors.
[skip]
RH It recovers my table but I end up with only 1030 out of 27497 rows,
RH so that's not a log of help!
RH Running myisamchk -r -e gives a similar result
Rolf,
Monday, September 02, 2002, 3:38:06 PM, you wrote:
RH I'm using MySQL 3.23.51. I have a table which started giving 127 errors.
[skip]
RH It recovers my table but I end up with only 1030 out of 27497 rows,
RH so that's not a log of help!
RH Running myisamchk -r -e gives a similar result
RH I'm using MySQL 3.23.51. I have a table which started giving 127 errors.
[skip]
RH It recovers my table but I end up with only 1030 out of 27497 rows,
RH so that's not a log of help!
RH Running myisamchk -r -e gives a similar result (only 1030 rows are
RH recovered), as does truncating the
At 23:57 +0100 9/2/02, Rolf Howarth wrote:
RH I'm using MySQL 3.23.51. I have a table which started giving 127 errors.
[skip]
RH It recovers my table but I end up with only 1030 out of 27497 rows,
RH so that's not a log of help!
RH Running myisamchk -r -e gives a similar result (only 1030 rows