Thanks for the replies, I will read that pdf file asap.

Paul, in response, I believe that I did, after the mishap I added
"innodb_file_per_table" to my.cnf file.

Mike, thanks for the information, I will have to take a look at the
PDF file and the options you layed out. It is possible that there
might be an issue with memory, however I doubt it since I had ZERO
problems prior to the server loosing power.

Thankfully this is on a test server that I just have all of my mail
forwarded to and no one else really uses it at this point, but I have
about 10 addresses forwarding to it for testing purposes of dbmail and
the webmail client that I am developing for it that connects directly
to the database.

I will let you know about what I find with the memory issues and file sizes.

Thanks much.
-Erik



On 10/31/05, M. J. [Mike] OBrien <[EMAIL PROTECTED]> wrote:
> Hi Erik:
> Sorry to hear about your mishap.
>
> I have seen before what you write about your _messageblks and assigned it to
> mismatched ibdata files and logs. Things look good for a while but as the
> system tries to run on a mismatched set of referenced relationships through
> the messages structure, you get peculiar manifestations which evolve into a
> totally and unpredictably confounded  _messageblks, _messages and more.
>
> You might think about your mail system's behaviour before it "restarted
> abruptly the other night due to power loss". Was it working well, prior? It
> seems strange that a sudden power down would cause this much harm. I wonder
> why things messed up in the first place?  Have you perhaps over or under
> allocated memory for Innodb buffers and logs? (Perhaps other folks might
> comment on buffer/log memory allotments.)
>
> Because of the recent mishaps-- are you using inadvertently all or part of
> your old log and ibdata files.
>
> Some notes:
> *innodb_buffer_pool_size*
> Allow as high as possible to minimize slow disk usage. You can set this up
> to 80% of the total available memory left after DBMail has what it needs to
> run *your* normal number of processes as set out in your dbmail.conf file.
>
> *innodb_log_file_size*
> should be up to 25 % of buffer pool size --some folks do much more (see
> perf. note below)
>
> *innodb_additional_mem_pool_size*
> stores the internal data structure--- big enough to store data about all
> your InnoDB tables
>
> For some interesting data on MySQL / InnoDB *performance*, check this out:
> http://dbma.ca/SourceLabsMySQLInnoDBScalabilityReport.pdf
>
>
> best... Mike
>
>
> ----- Original Message -----
> From: "Erik Kristensen" <[EMAIL PROTECTED]>
> To: "DBMail mailinglist" <dbmail@dbmail.org>
> Sent: Sunday, October 30, 2005 9:00 AM
> Subject: [Dbmail] mysql innodb dbmail_messageblks getting corrupt
>
>
> Morning everyone,
>
> Over the last few days I have been having some very frustrating
> experience with dbmail and I haven't been able to totally narrow it
> down to an issue with the server, mysql server, or dbmails injection
> into the database.
>
> dbmail version: 2.0.7
>
> Apparently the server that I am having these issues with restarted
> abruptly the other night due to power loss, at which time it seems
> that the database got corrupt. I was able to do innodb_force_recovery
> = 1 in the my.cnf file so that I could get a clean dump of the
> database since my other backup solution had failed ....
>
> After I got the clean dump of the database, I dropped my old dbmail
> database completely that still had corrupt data in it. I recreated the
> database inserted the data back into the system from the dump file.
> Everything seem to work fine for several hours .... last night the db
> was showing up corrupt again ... and it is only the dbmail_messageblks
> table that is showing corrupt.
>
> Anyone else had issues? Anyone have any ideas? Thanks ...
>
> -Erik
> _______________________________________________
> Dbmail mailing list
> Dbmail@dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>
> _______________________________________________
> Dbmail mailing list
> Dbmail@dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>

Reply via email to