Hello!

I'm running FreeBSD 6.2 with mysql-4.1.22 and noticed two problems:

1) mysqld takes lots of processor time during its work. Today I found
it was using 454:20. After restart everything got back to normal, but
after few hours it started to use 5:15 and increasing. Playing with
confing gave no results. Is it mysql bug?

2) mysql says: "Error: Got error 130 from storage engine" on one of my
tables, but repair table, can't fix it. Is it safe to to run
"myisamchk"?

Thanks, and sorry for my bad English. If you know where to read about
such problems and have no time to answer, please send my the links.

On Sat, 29 Mar 2008 00:54:45 -0700 (PDT), Tolik Piskov wrote:
> Hello!
>
> I'm running FreeBSD 6.2 with mysql-4.1.22 and noticed two problems:
>
> 1) mysqld takes lots of processor time during its work. Today I found
> it was using 454:20. After restart everything got back to normal, but
> after few hours it started to use 5:15 and increasing. Playing with
> confing gave no results. Is it mysql bug?

So MySQL has used 5 and a quarter minutes of CPU time over a few hours.
That sound perfectly reasonable to me. My lightly-used installation has
used 200 minutes in a half-year.

> 2) mysql says: "Error: Got error 130 from storage engine" on one of my
> tables, but repair table, can't fix it. Is it safe to to run
> "myisamchk"?

Probably won't . If I remember correctly, 130 errors generally mean
that one of the table files is trash.

$ perror 130
MySQL error code 130: Incorrect file format

Yup. I hope you had a recent backup.

> Thanks, and sorry for my bad English. If you know where to read about
> such problems and have no time to answer, please send my the links.


--
Progress (n.): The process through which Usenet has evolved from
smart people in front of dumb terminals to dumb people in front
of smart terminals.
-- obs@burnout.demon.co.uk