免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 3655 | 回复: 1
打印 上一主题 下一主题

innobackupex恢复报错,请高人指点 [复制链接]

论坛徽章:
8
数据库技术版块每日发帖之星
日期:2015-12-22 06:20:00数据库技术版块每日发帖之星
日期:2015-12-23 06:20:00数据库技术版块每周发帖之星
日期:2016-02-03 16:55:09数据库技术版块每日发帖之星
日期:2016-07-15 06:20:00IT运维版块每日发帖之星
日期:2016-08-13 06:20:00数据库技术版块每日发帖之星
日期:2016-08-15 06:20:00IT运维版块每日发帖之星
日期:2016-08-16 06:20:00IT运维版块每日发帖之星
日期:2016-08-17 06:20:00
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2015-12-20 16:25 |只看该作者 |倒序浏览
[root@zhancat200805 data]# innobackupex --defaults-file=/usr/local/mysql/my.cnf --copy-back --rsync /tmp/mysql/full
151220 16:23:39 innobackupex: Starting the copy-back operation

IMPORTANT: Please check that the copy-back run completes successfully.
           At the end of a successful copy-back run innobackupex
           prints "completed OK!".

innobackupex version 2.3.2 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 306a2e0)
2015-12-20 16:23:39 7ff5740fd720  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
[01] error: cannot open file ibdata1
2015-12-20 16:23:39 7ff5740fd720  InnoDB: Operating system error number 9 in a file operation.
InnoDB: Error number 9 means 'Bad file descriptor'.
InnoDB: Some operating system error numbers are described at
InnoDB: File (unknown): 'close' returned OS error 109. Cannot continue operation
2015-12-20 16:23:39 7ff5740fd720  InnoDB: Assertion failure in thread 140692190910240 in file os0file.cc line 658
InnoDB: We intentionally generate a memory trap.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
08:23:39 UTC - xtrabackup got signal 6 ;
This could be because you hit a bug or data is corrupted.
This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x10000
innobackupex(my_print_stacktrace+0x2e) [0x92c04e]
innobackupex(handle_fatal_signal+0x235) [0x830c15]
/lib64/libpthread.so.0() [0x38d980f790]
/lib64/libc.so.6(gsignal+0x35) [0x38d9432625]
/lib64/libc.so.6(abort+0x175) [0x38d9433e05]
innobackupex() [0x5ab701]
innobackupex(os_file_close_func(int)+0x2 [0x5acea8]
innobackupex(copy_file(char const*, char const*, unsigned int)+0x32b) [0x589bfb]
innobackupex(copy_back()+0x44b) [0x58a43b]
innobackupex(main+0x7f7) [0x57ba87]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x38d941ed5d]
innobackupex(__gxx_personality_v0+0x351) [0x56f909]

报错原因如上面所示,读不懂是什么意思,请高人指点,谢谢!

论坛徽章:
6
数据库技术版块每日发帖之星
日期:2015-10-11 06:20:00数据库技术版块每日发帖之星
日期:2015-10-12 06:20:00数据库技术版块每日发帖之星
日期:2015-10-15 06:20:00数据库技术版块每日发帖之星
日期:2015-10-30 06:20:00综合交流区版块每月发帖之星
日期:2015-12-02 14:59:01数据库技术版块每日发帖之星
日期:2015-12-15 06:20:00
2 [报告]
发表于 2015-12-21 16:36 |只看该作者
数据库没停止,进行的恢复作业?
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP