1) myisam or innodb? 2) could it be a table size limitation? what OS are you running under?
I had similar trouble with myisam because of table size problems, I split them into multiple tables and set messageblks as one large merge table.. -Sri On Fri, April 8, 2005 12:00 pm, Jason Burfield said: > I'm running a bit of an older version of dbmail (1.2.9) with MySQL 4.0.12 > and as of yesterday I have started having problems. > > The problem is with dbmail-maintenance. > > It is being run on a cron each night with the following options: > > dbmail-maintenance -cfpd > > This has been working flawlessly for the past year+. > > However, starting 2 nights ago, when running dbmail-maintenance -cfpd it > causes the messageblks table to become corrupt. > > The output from 'check table' within MySQL results in: > > mysql> check table messageblks; > +--------------------+-------+----------+-----------------------------------------------------+ > | Table | Op | Msg_type | Msg_text > | > +--------------------+-------+----------+-----------------------------------------------------+ > | dbmail.messageblks | check | warning | Table is marked as crashed and > last repair failed | > | dbmail.messageblks | check | warning | Size of indexfile is: 15710208 > Should be: 1024 | > | dbmail.messageblks | check | error | Can't read indexpage from > filepos: -1 | > | dbmail.messageblks | check | error | Corrupt > | > +--------------------+-------+----------+-----------------------------------------------------+ > > > I am able to rebuild the table and all is well again. However, on the next > dbmail-maintenance run it corrupts the table once again. > > That table (messageblks) is 3 gigs in size. > > I checked through the past messages but was unable to find anything. I > also checked the bug list but didn't see anything in there either. > > Anyone have any ideas on this one? > > Thanks! > > -- Jason
