Bug #65596 mysqldump Error 2013: Lost connection to MySQL server during query when dumping
Submitted: 13 Jun 2012 6:53 Modified: 24 Jun 2012 5:34
Reporter: wu mg Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.5.8-log MySQL Community Server (GPL) OS:Microsoft Windows (win7)
Assigned to: CPU Architecture:Any
Tags: 2013, Lost connection, mysqldump

[13 Jun 2012 6:53] wu mg
Description:
Hi, when i backup database by using mysqldump tool, it report error 2013

mysqldump -uuser -ppwd dbname  > d:/backup.sql
mysqldump: Error 2013: Lost connection to MySQL server during query when dumping
 table `o_log_xxxxxxx` at row: 4600

error row is not fixed, sometimes change to another number such as 4544

i can execute query normal in the error table, such as "select * from o_log_xxxxxxx limit 10", and get correct result

i search some reported bugs, and change max_allowed_packet from 10M to 500M, but get same result.

is there any suggestion?

mysql error log:
120613 14:26:12  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 3130291633:962663424, should be 0:3282!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3282.
InnoDB: You may have to recover from a backup.
120613 14:26:12  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 47494638396114001400d53f00b98721fde56a966712fedd5afce58fffe354fed536ba9475b19cd8fef7d8fffffeffdd44946aab8f5877fbcc33a976166b31a3ffe65bfcb42cfebb1bffdb47fdb513ffe04effe349ffcb2cfeefa0fdb44bfaab39fdf1c5e6bf40ffbe12d1a952895a0cdab53cd09017f4d24bfed443fed44edfc792ead4a5faa822fcbd51fcebb5e8d8cbffe2407d55baeee8e279500bfdce5cfefdf19c7530fde436da9b37f9f4eaf3f1fbf6fdfff99b3fd8c7afe3a940e5b12dfbdf7df7b91fd4b367ffffff21f9040100003f002c00000000140014000006e0c09f70482c1a8b8b8b7279245a16148bd4b2b4349f9d88b6300a7528136bd1d2793d02016d08243018c2484b20a3caa4030402ef3d4166140a310a190b198281307042491c0a36082d07333e0c08801c1e15430b168d2b10a01f0da0370a09999b05042a040c100d061fa02b1c3ca88b050552142c0e3b0e0e181b1b12139a8b16b9115c02cd023429291a12c73f0b24251103253a0735260f0f1ae3156242181411251b2780350002381b15d5421618182428ed0a2e320f28e8991b720f438f0f26721c102042e0150c1344086003c061937318003ca057efa2c78f207f0401003b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000120613 14:26:12  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 4276712445:962663424, should be 0:3298!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3298.
InnoDB: You may have to recover from a backup.
120613 14:26:12  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 47000000004946000038390000611400000014000000d500003f000000ffd500003bfe0000ea880000f7d7000052fe00b4001500ff00ff00fe00ff00fa00e700ff00da004400fe00e9007300fd00cd003200ee00a8001a00fe00ca005800f600b7002600ff00e0004d009500000068160000fec2000025fe0000c62e0000ffe400000054ff0000e1490000feb7000019ff0000cb2c0000f8b00000188900005a0c0000fdf10000c5fe0000efa00000bf86000013e80000b8370000f8b200001cf50000b11d0000feba00001dff0000ec5200006a300000a5b9000087220000ca9400002eef0000ebf800fbdf7debca4cffd82afcebb5ffce239772bdcdbbdeffee5d0000007d550000bafe0000f7d80000ffe500004ca590dbdfd4edfff46fffc118eec133ffb70cffdf4aa27419f1ba31f7f4f9fffdf3e6bf40ffe65de7c862f5d044fed443d09017fbe264ffffff21f9040100003f002c00000000140014000006e1c09f70482c1a8fc8e48fc164743a06e59299823020500303c9880840a0516af401f126db62d7db68e85eb80a0d3141172300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000091c3ea762b5c7207162522000f771704042104162401362e0437250f693f780504281e2a8d01271e2704050f1243112c16892a2d222622211e288c0ea64211100117bb0102080a160505160a1c1ca7560606002400cb263003320312b697ce0c3e3b3119dd350914d4d5a71306333b0d15eaeb3de2963f13080033191f1f18f818e014d6420c130e102c7bb060c3060d1aaabdf3378183030705112650c86502858be1f8495868c4a2c67152420e0902003b0000...lost of 0...000a corrupt database page.

How to repeat:
mysqldump
[13 Jun 2012 7:43] Valeriy Kravchuk
Looks like your data are corrupted, probably because of hardware failure. So, please, upgrade to recent version, 5.5.25, restore data from backup and then check if this error will ever happen again.
[24 Jun 2012 5:34] wu mg
ok