V2EX = way to explore
V2EX 是一个关于分享和探索的地方
现在注册
已注册用户请  登录
V2EX 提问指南
54dev
V2EX  ›  问与答

数据库里的数据导不出来了,是不是数据损坏了?

  •  
  •   54dev · 2013-07-24 16:42:25 +08:00 · 2540 次点击
    这是一个创建于 3930 天前的主题,其中的信息可能已经有所发展或是发生改变。
    mysqldump: Got error: 2013: Lost connection to MySQL server during query when using LOCK TABLES

    表是innodb的。

    百度上的结果让去修改mysql的一些参数,但无效。

    在GOOGLE上搜的第一条结果就是要修改表了

    求dba高手指导。
    3 条回复    1970-01-01 08:00:00 +08:00
    nybux
        1
    nybux  
       2013-07-24 17:10:33 +08:00
    看看mysql的错误日志
    54dev
        2
    54dev  
    OP
       2013-07-24 17:18:05 +08:00
    54dev
        3
    54dev  
    OP
       2013-07-24 17:18:12 +08:00
    @nybux
    130724 11:13:15 [Note] Plugin 'FEDERATED' is disabled.
    130724 11:13:15 InnoDB: Initializing buffer pool, size = 2.0G
    130724 11:13:16 InnoDB: Completed initialization of buffer pool
    InnoDB: Log scan progressed past the checkpoint lsn 68 990469989
    130724 11:13:16 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 68 990540111
    InnoDB: Transaction 0 1257862957 was in the XA prepared state.
    InnoDB: 1 transaction(s) which must be rolled back or cleaned up
    InnoDB: in total 0 row operations to undo
    InnoDB: Trx id counter is 0 1257863424
    130724 11:13:16 InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percents: 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
    InnoDB: Apply batch completed
    InnoDB: Last MySQL binlog file position 0 11814, file name ./mysql-bin.000040
    130724 11:13:17 InnoDB: Started; log sequence number 68 990540111
    130724 11:13:17 [Note] Recovering after a crash using mysql-bin
    130724 11:13:17 [Note] Starting crash recovery...
    130724 11:13:17 InnoDB: Starting recovery for XA transactions...
    130724 11:13:17 InnoDB: Transaction 0 1257862957 in prepared state after recovery
    130724 11:13:17 InnoDB: Transaction contains changes to 1 rows
    130724 11:13:17 InnoDB: 1 transactions in prepared state after recovery
    130724 11:13:17 [Note] Found 1 prepared transaction(s) in InnoDB
    InnoDB: Starting in background the rollback of uncommitted transactions
    130724 11:13:17 InnoDB: Rollback of non-prepared transactions completed
    130724 11:13:17 [Note] Crash recovery finished.
    130724 11:13:17 [Note] Event Scheduler: Loaded 0 events
    130724 11:13:17 [Note] /web/database/bin/mysqld: ready for connections.
    Version: '5.1.66-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
    关于   ·   帮助文档   ·   博客   ·   API   ·   FAQ   ·   我们的愿景   ·   实用小工具   ·   5366 人在线   最高记录 6543   ·     Select Language
    创意工作者们的社区
    World is powered by solitude
    VERSION: 3.9.8.5 · 28ms · UTC 08:20 · PVG 16:20 · LAX 01:20 · JFK 04:20
    Developed with CodeLauncher
    ♥ Do have faith in what you're doing.