mysqldump. There are other users, but the behavior recurs even if the
database is only being used by mysqldump.
Thanks,
LA
Michael Dykman wrote:
How are you performing the backup? What tools are involved? Are
there any ther users of the database while you are doing this?
- michael dykman
On Wed, Sep 3, 2008 at 4:43 PM, L'argent <[EMAIL PROTECTED]> wrote:
I've been trying to backdown a production database for some time and can't
seem to get around MySQL crashing at about 1GB of backup data. (the database
is about 400GB).
I have a page corruption, but it isn't found when I do a CHECK TABLE on
*any* of the tables. InnoDB is running in super-safe (double-write) mode.
The most recent crash spit out this memory status:
Memory status:
Non-mmapped space allocated from system: 541413376
Number of free chunks: 7121
Number of fastbin blocks: 0
Number of mmapped regions: 18
Space in mmapped regions: -2063269888
Maximum total allocated space: 0
Space available in freed fastbin blocks: 0
Total allocated space: 478166624
Total free space: 63246752
Top-most, releasable space: 749360
Estimated memory (with thread stack): -1327869952
---
All those negative numbers make me believe its a MySQL bug rather than a
data corruption issue.
The server is now running 5.0.67 (redhat x86_64) Community. The server has
16 GB of ram and 8 cores and 6 RAID 1 arrays with the InnoDB files split
amongst each.
Any suggestions on where to look to get this figured out?
thanks in advance,
LA
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
