centos – 快照期间的错误页面映射错误

CentOS 前端之家
前端之家收集整理的这篇文章主要介绍了centos – 快照期间的错误页面映射错误，前端之家小编觉得挺不错的，现在分享给大家，也给大家做个参考。
我运行以下命令来创建快照卷.但内核收到了一个错误,kvm管理程序停止响应.为什么错误以及如何解决？ 
  1. lvcreate -L20G -s -n volume_A_backup /dev/vgroup/volumeA

错误日志：

  1. Mar 10 02:36:59 kvm kernel: BUG: Bad page map in process udevd  pte:800000081ad43645 pmd:409f37067
  2. Mar 10 02:36:59 kvm kernel: addr:00006aff4f837000 vm_flags:00100173 anon_vma:ffff88081f7dc448 mapping:(null) index:7fffffff1
  3. Mar 10 02:37:02 kvm kernel: Pid: 5091,comm: udevd Not tainted 2.6.32-358.18.1.el6.x86_64 #1
  4. Mar 10 02:37:03 kvm kernel: Call Trace:
  5. Mar 10 02:37:03 kvm kernel: [<ffffffff8113ef18>] ? print_bad_pte+0x1d8/0x290
  6. Mar 10 02:37:03 kvm kernel: [<ffffffff8111b970>] ? generic_file_aio_read+0x380/0x700
  7. Mar 10 02:37:03 kvm kernel: [<ffffffff8113f03b>] ? vm_normal_page+0x6b/0x70
  8. Mar 10 02:37:03 kvm kernel: [<ffffffff8114179f>] ? unmap_vmas+0x61f/0xc30
  9. Mar 10 02:37:03 kvm kernel: [<ffffffff811476d7>] ? exit_mmap+0x87/0x170
  10. Mar 10 02:37:03 kvm kernel: [<ffffffff8106b50c>] ? mmput+0x6c/0x120
  11. Mar 10 02:37:03 kvm kernel: [<ffffffff811889a4>] ? flush_old_exec+0x484/0x690
  12. Mar 10 02:37:03 kvm kernel: [<ffffffff811d9700>] ? load_elf_binary+0x350/0x1ab0
  13. Mar 10 02:37:03 kvm kernel: [<ffffffff8113f3ff>] ? follow_page+0x31f/0x470
  14. Mar 10 02:37:03 kvm kernel: [<ffffffff811446e0>] ? __get_user_pages+0x110/0x430
  15. Mar 10 02:37:03 kvm kernel: [<ffffffff811d7abe>] ? load_misc_binary+0x9e/0x3f0
  16. Mar 10 02:37:03 kvm kernel: [<ffffffff81144a99>] ? get_user_pages+0x49/0x50
  17. Mar 10 02:37:03 kvm kernel: [<ffffffff81189fa7>] ? search_binary_handler+0x137/0x370
  18. Mar 10 02:37:03 kvm kernel: [<ffffffff8118a4f7>] ? do_execve+0x217/0x2c0
  19. Mar 10 02:37:03 kvm kernel: [<ffffffff810095ea>] ? sys_execve+0x4a/0x80
  20. Mar 10 02:37:03 kvm kernel: [<ffffffff8100b4ca>] ? stub_execve+0x6a/0xc0
  21. Mar 10 02:37:03 kvm kernel: Disabling lock debugging due to kernel taint
  22. Mar 10 02:37:03 kvm kernel: BUG: Bad page map in process dmsetup  pte:00000700 pmd:409f34067
  23. Mar 10 02:37:03 kvm kernel: addr:00006a3dcd3df000 vm_flags:08000070 anon_vma:(null) mapping:ffff88081b8385e0 index:27
  24. Mar 10 02:37:03 kvm kernel: vma->vm_ops->fault: filemap_fault+0x0/0x500
  25. Mar 10 02:37:03 kvm kernel: vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60 [ext4]
  26. Mar 10 02:37:04 kvm kernel: Pid: 5091,comm: dmsetup Tainted: G    B      ---------------    2.6.32-358.18.1.el6.x86_64 #1
  27. Mar 10 02:37:04 kvm kernel: Call Trace:
  28. Mar 10 02:37:04 kvm kernel: [<ffffffff8113ef18>] ? print_bad_pte+0x1d8/0x290
  29. Mar 10 02:37:04 kvm kernel: [<ffffffff8113f03b>] ? vm_normal_page+0x6b/0x70
  30. Mar 10 02:37:04 kvm kernel: [<ffffffff8114179f>] ? unmap_vmas+0x61f/0xc30
  31. Mar 10 02:37:04 kvm kernel: [<ffffffff811476d7>] ? exit_mmap+0x87/0x170
  32. Mar 10 02:37:04 kvm kernel: [<ffffffff8106b50c>] ? mmput+0x6c/0x120
  33. Mar 10 02:37:04 kvm kernel: [<ffffffff8107312b>] ? exit_mm+0x12b/0x180
  34. Mar 10 02:37:04 kvm kernel: [<ffffffff810734df>] ? do_exit+0x15f/0x870
  35. Mar 10 02:37:04 kvm kernel: [<ffffffff81073c48>] ? do_group_exit+0x58/0xd0
  36. Mar 10 02:37:04 kvm kernel: [<ffffffff81073cd7>] ? sys_exit_group+0x17/0x20
  37. Mar 10 02:37:04 kvm kernel: [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
  38. Mar 10 02:37:04 kvm kernel: BUG: Bad page map in process dmsetup  pte:00000f00 pmd:409f34067
  39. Mar 10 02:37:04 kvm kernel: addr:00006a3dcd3ef000 vm_flags:08000070 anon_vma:(null) mapping:ffff88081b8385e0 index:37
  40. Mar 10 02:37:04 kvm kernel: vma->vm_ops->fault: filemap_fault+0x0/0x500
  41. Mar 10 02:37:05 kvm kernel: vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60 [ext4]
  42. Mar 10 02:37:05 kvm kernel: Pid: 5091,comm: dmsetup Tainted: G    B      ---------------    2.6.32-358.18.1.el6.x86_64 #1
  43. Mar 10 02:37:05 kvm kernel: Call Trace:
  44. Mar 10 02:37:05 kvm kernel: [<ffffffff8113ef18>] ? print_bad_pte+0x1d8/0x290
  45. Mar 10 02:37:05 kvm kernel: [<ffffffff8113f03b>] ? vm_normal_page+0x6b/0x70
  46. Mar 10 02:37:05 kvm kernel: [<ffffffff8114179f>] ? unmap_vmas+0x61f/0xc30
  47. Mar 10 02:37:05 kvm kernel: [<ffffffff811476d7>] ? exit_mmap+0x87/0x170
  48. Mar 10 02:37:05 kvm kernel: [<ffffffff8106b50c>] ? mmput+0x6c/0x120
  49. Mar 10 02:37:05 kvm kernel: [<ffffffff8107312b>] ? exit_mm+0x12b/0x180
  50. Mar 10 02:37:05 kvm kernel: [<ffffffff810734df>] ? do_exit+0x15f/0x870
  51. Mar 10 02:37:05 kvm kernel: [<ffffffff81073c48>] ? do_group_exit+0x58/0xd0
  52. Mar 10 02:37:05 kvm kernel: [<ffffffff81073cd7>] ? sys_exit_group+0x17/0x20
  53. Mar 10 02:37:05 kvm kernel: [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
  54. Mar 10 02:37:05 kvm kernel: BUG: Bad page map in process dmsetup  pte:00000f00 pmd:409f35067
  55. Mar 10 02:37:05 kvm kernel: addr:00006a3dcd447000 vm_flags:08000070 anon_vma:(null) mapping:ffff88081b8385e0 index:8f
  56. Mar 10 02:37:05 kvm kernel: vma->vm_ops->fault: filemap_fault+0x0/0x500
  57. Mar 10 02:37:05 kvm kernel: vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60 [ext4]
  58. Mar 10 02:37:05 kvm kernel: Pid: 5091,comm: dmsetup Tainted: G    B      ---------------    2.6.32-358.18.1.el6.x86_64 #1
  59. Mar 10 02:37:05 kvm kernel: Call Trace:
  60. Mar 10 02:37:05 kvm kernel: [<ffffffff8113ef18>] ? print_bad_pte+0x1d8/0x290
  61. Mar 10 02:37:05 kvm kernel: [<ffffffff8112f42e>] ? __put_single_page+0x1e/0x30
  62. Mar 10 02:37:05 kvm kernel: [<ffffffff8113f03b>] ? vm_normal_page+0x6b/0x70
  63. Mar 10 02:37:05 kvm kernel: [<ffffffff8114179f>] ? unmap_vmas+0x61f/0xc30
  64. Mar 10 02:37:05 kvm kernel: [<ffffffff811476d7>] ? exit_mmap+0x87/0x170
  65. Mar 10 02:37:05 kvm kernel: [<ffffffff8106b50c>] ? mmput+0x6c/0x120
  66. Mar 10 02:37:05 kvm kernel: [<ffffffff8107312b>] ? exit_mm+0x12b/0x180
  67. Mar 10 02:37:05 kvm kernel: [<ffffffff810734df>] ? do_exit+0x15f/0x870
  68. Mar 10 02:37:05 kvm kernel: [<ffffffff81073c48>] ? do_group_exit+0x58/0xd0
  69. Mar 10 02:37:05 kvm kernel: [<ffffffff81073cd7>] ? sys_exit_group+0x17/0x20
  70. Mar 10 02:37:05 kvm kernel: [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
  71. Mar 10 02:37:05 kvm kernel: BUG: Bad page map in process dmsetup  pte:00000300 pmd:409f35067
你的内核被污染了： 
  1. Tainted: G    B

B表示[1]：

A process has been found in a Bad page state,indicating a corruption of the virtual memory subsystem,possibly caused by malfunctioning RAM or cache memory.

基本上大多数BUG：正在处理的错误页面映射与物理内存故障有关.但在存在虚拟化的情况下,它也可能是一个hypervizor bug.
但我建议你先检查一下mcelog(8).

[1] http://www.novell.com/support/kb/doc.php?id=3582750

猜你在找的CentOS相关文章

Centos7离线安装gcc4.8
有时候CentOS工作在无互联网的环境下，需要在离线环境下安装一些组件，这次实现的是模拟在...
CentOS7离线安装devtoolset-9并编译redis6.0.5
首先参照https://www.cnblogs.com/wdw984/p/13330074.html，来进行如何安装Centos和离线下...
使用Nginx在80端口上代理多个.NET CORE网站
有两个.NET CORE3.1网站部署在CentOS7上（内网IP是192.168.2.32），现在想实现访问http://...
CentOS7中配置vsftpd
1、yum -y install vsftpd 安装vsftpd 2、配置vsftpd的配置文件（/etc/vsftpd/vsftpd.conf...
CentOS7离线安装Mysql8.0
首先去mysql官网下载mysql的离线rpm安装包（https://downloads.mysql.com/archives/commun...
CentOS中增加网络连接数的方法
CentOS默认对外访问，发起的TCP链接总数小于28232个。 可以通过以下命令的结果计算出来 $ ...
VMware安装Centos7虚拟机
首先安装虚拟机很简单，所以呢，具体的安装过程就引用别人的博客，这篇文字很详细，引用之...
[Linux] 解决CentOS下Requires: libjson-c.so错误
当安装某些rpm包的时候 , 会爆出这个错误 Requires: libjson-c.so json-c是c语言下的json库...
阿里云centos7安装mysql8数据库
linux系统安装mysql8
centos安装mysql
一、安装 二、修改密码 三、修改远程连接权限(为了使用navicat)
LinuxWindowsCentOSUbuntuNginxWebServiceScalaMemcacheApacheRedisDockerBashAzureTomcatLNMPShell数据结构服务器运维网络安全
xebugnodemondocker-copydcoselasticsearcwindows-contdocker-windodocker-awsamazon-cloudenvoyproxyhashicorp-vaswisscomdevkafka-pythonzscalerphoton-osdocker-swarmkamongoogle-cloudconcoursewso2-ampersistent-vapi-managerprocess-manamanjarojenkins-workhypriotremoteapikeystonejsbitcoindbitcoin-test