k8s使用glusterfs存储报错type ‘features/utime‘

k8s使用glusterfs存储报错type ‘features/utime‘ is not valid or not found on this machine

pods报错如下

Events:
  Type     Reason       Age    From                    Message
  ----     ------       ----   ----                    -------
  Normal   Scheduled    5m48s  default-scheduler       Successfully assigned default/auth-web-1-77f4f7cbcc-snp8c to 192.168.1.216
  Warning  FailedMount  5m47s  kubelet, 192.168.1.216  MountVolume.SetUp failed for volume "auth-web-home" : mount failed: mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t glusterfs -o log-file=/var/lib/kubelet/plugins/kubernetes.io/glusterfs/auth-web-home/auth-web-1-77f4f7cbcc-snp8c-glusterfs.log,backup-volfile-servers=192.168.1.175:192.168.1.178:192.168.1.179,log-level=ERROR 192.168.1.175:k8s-glusterfs /var/lib/kubelet/pods/cb033ec1-6a62-11e9-b923-e0d55e1cf4c9/volumes/kubernetes.io~glusterfs/auth-web-home
Output: Mount failed. Please check the log file for more details.

 the following error information was pulled from the glusterfs log to help diagnose this issue:
[2019-04-29 09:40:16.070806] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:16.071117] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x5654d1b3138e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x5654d1b2bdc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f7989cda68b] ) 0-graph: invalid argument: graph [Invalid argument]
  Warning  FailedMount  5m47s  kubelet, 192.168.1.216  MountVolume.SetUp failed for volume "auth-web-home" : mount failed: mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t glusterfs -o log-level=ERROR,log-file=/var/lib/kubelet/plugins/kubernetes.io/glusterfs/auth-web-home/auth-web-1-77f4f7cbcc-snp8c-glusterfs.log,backup-volfile-servers=192.168.1.175:192.168.1.178:192.168.1.179 192.168.1.175:k8s-glusterfs /var/lib/kubelet/pods/cb033ec1-6a62-11e9-b923-e0d55e1cf4c9/volumes/kubernetes.io~glusterfs/auth-web-home
Output: Mount failed. Please check the log file for more details.

根据报错信息,我们可以看出来挂载的时候他是指定的日志文件的,我们去对应的日志查看报错

[2019-04-29 09:40:16.070575] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
[2019-04-29 09:40:16.070647] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:16.070806] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:16.071117] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x5654d1b3138e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x5654d1b2bdc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f7989cda68b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:16.712383] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
[2019-04-29 09:40:16.712464] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:16.712658] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:16.713034] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55c7459fe38e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55c7459f8dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f1a3cded68b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:17.868659] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
[2019-04-29 09:40:17.868718] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:17.868882] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:17.869215] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x5625d510738e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x5625d5101dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f578831768b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:20.068908] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
[2019-04-29 09:40:20.068976] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:20.069168] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:20.069562] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55da540e838e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55da540e2dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f1a9d62068b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:24.271395] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
[2019-04-29 09:40:24.271482] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:24.271669] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:24.272034] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x56378367338e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x56378366ddc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f676cb0468b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:32.670859] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
[2019-04-29 09:40:32.670935] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:32.671118] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:32.671504] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55d7af7e738e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55d7af7e1dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7f33da2a568b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:40:48.870810] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
[2019-04-29 09:40:48.870865] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:40:48.871021] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:40:48.871325] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55b23825838e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55b238252dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7fcc6bb9668b] ) 0-graph: invalid argument: graph [Invalid argument]
[2019-04-29 09:41:21.069815] E [MSGID: 101002] [graph.y:212:volume_type] 0-parser: Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
[2019-04-29 09:41:21.069878] E [MSGID: 101019] [graph.y:320:volume_end] 0-parser: "type" not specified for volume k8s-glusterfs-utime
[2019-04-29 09:41:21.070033] E [MSGID: 100026] [glusterfsd.c:2307:glusterfs_process_volfp] 0-: failed to construct the graph
[2019-04-29 09:41:21.070404] E [graph.c:982:glusterfs_graph_destroy] (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x12e) [0x55c07e7d838e] -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x148) [0x55c07e7d2dc8] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(glusterfs_graph_destroy+0x6b) [0x7fe065eee68b] ) 0-graph: invalid argument: graph [Invalid argument]

发现他一直在提示这一句 Volume ‘k8s-glusterfs-utime‘, line 61: type ‘features/utime‘ is not valid or not found on this machine
造成这个原因有如下几种可能:
1,glusterfs-server和glusterfs-client安装的版本不对应(解决办法,升级版本使版本一致)
2,glusterfs-server和glusterfs-clinet时间不同步,(做ntp时间服务器,或者关闭校验使用命令 gluster volume set $VolumeName ctime off)

原文地址：https://blog.51cto.com/13447608/2386823

时间： 2024-10-14 22:18:57

k8s使用glusterfs存储报错type ‘features/utime‘的相关文章

Esxi6.0-U1 宿主机挂载EMC存储报错

时间:2016-7-4 事件:esxi6.0主机挂载存储报错 解决办法: 原来这是vSphere 6的一个已知bug,解决方法是重启管理代理,方法有两种. 一是去ESXi主机控制台上按F2,以root登陆,然后选择Restart Management Agents. 二是通过SSH登陆ESXi主机.具体步骤如下: 用Client登陆vCenter,找到这台主机,在其Configuration中选择Security Profile,点右边的Properties 在列表中选择SSH,点击Option

爬坑PIL，文件名Image与类Image()重名,导致引用new,open不成功，报错 type object 'Image' has no attribute 'new'

网上的东西真坑人啊 在知乎里看到的最有意思的python项目,于是选了一个qrcode二维码的项目来自己尝试 github里下载到pycharm之后就开始了踩坑之路. 先说安装pillow 升级pip到19.2.3版本之后,安装pillow(pip install pillow) 之后尝试导入 import Pillow / import pillow / import PIL 死活没有,我很纳闷.卸了重装都没效果依旧导入失败. 然后手动查找到底有没有,于是打开site-package. 大爷的

七牛云存储 报错的问题

上传 401 错误码 liangchao • 发表于:2015年08月20日 15:26 • 更新于:2016年01月07日 17:01 一.报错:{"error":"expired token"},{“error”:”token out of date”} 处理方法: 1.将token的有效期设置的长一些.对于比较大的文件,可以适当加长有效期(默认是3600秒) 2.看下自己的服务器时间是否是联网时间.如果时间不准,导致签名后的结果可能已经是过期的了 3.建议客户

报错 Type interface *** is not known to the MapperRegistry. 的解决方案

今天我在学习mybatis时碰到了这个报错:org.apache.ibatis.binding.BindingException: Type interface *** is not known to the MapperRegistry. 通过搜索引擎找了很久之后都没能找到解决方案,网上流传的比较多的解决方案是:mapper.xml文件放置到跟接口DAO.java不同名,或者是mapper.xml的namespace没有写对.但是我的错误都不是上述问题. 后来我想了想,我在写完mapper.x

Xcode CoreData 存储报错问题。

因项目接口变动,导致之前的CoreData字段需要调整.于是记录下出错的流程和解决方案.步骤如下: 1. 先在 *****.xcdatamodeld 文件中添加需要调整的字段.并更新本地model实体. 2. 我的流程是接到消息后本地存储在CoreData里面,然后UI展示(具体消息推送和接收问题,之前已经做好了,不在这里讲解.).因我是真机调试,收到消息推送后,但是一直无数据.于是想去本地sqlite里面查看是否已经将消息存储完毕,于是捕捉到路径并执行进入sqlite时问题来了: sqlite

k8s 对接glusterfs存储

service 与 endpoint 是通过namespace相同,name相同,相互关联的 创建endpoint [[email protected] glusterfs]# cat glusterfs-ep.yaml apiVersion: v1 kind: Endpoints metadata: name: glusterfs namespace: tomcat subsets: - addresses: - ip: 10.0.0.11 - ip: 10.0.0.12 - ip: 10.0

jauery改变inout的type属性报错type property can’t be changed

uncaught exception type property can't be changed 使用代码$("#pwd").attr("type","password")时出现上面的错误. 猜测是该版本jQuery不允许修改控件type属性,使用原生js语句可以解决这个问题. [javascript] view plain copy $("#txtpwd").focus(function () { if ($(this).

Android报错Type Error executing aapt: Return code -1

我的做法是(乱蒙对的) 把menu.xml干掉!,对的你没看错! 当然其他人方案:如下 1.http://stackoverflow.com/questions/10699439/aapt-filing-with-error-code-1073741819 2.http://blog.csdn.net/forlong401/article/details/23919633 3.http://www.tuicool.com/articles/muYN32

mysql表情存储报错问题

mysql采用utf-8字符编码,但在移动端使用输入法的表情并存储数据库的时候,出现错误. java.sql.SQLException: Incorrect string value: '\xF0\x9F\x92\x94'... 经排查,原因在于utf-8编码无法存储表情字符. 解决步骤: 更改数据库编码为utf8mb4和utf8mb4_unicode_ci 更改所需要存储表情的那张表的编码为utf8mb4和utf8mb4_unicode_ci 更改表中存储的那个字段的编码为utf8mb4和ut