gluster brick進程啟動失敗怎么處理

這篇文章主要講解了“gluster brick進程啟動失敗怎么處理”，文中的講解內容簡單清晰，易于學習與理解，下面請大家跟著小編的思路慢慢深入，一起來研究和學習“gluster brick進程啟動失敗怎么處理”吧！

環境說明：

    復制卷，centos 7下，gluster版本3.6.7

故障現象：

# gluster v status tank

Status of volume: tank

Gluster processPortOnlinePid

------------------------------------------------------------------------------

Brick w-ostack03.sys.bjdt.net:/data/tank49152Y30371

Brick w-ostack04.sys.bjdt.net:/data/tankN/ANN/A

NFS Server on localhost2049Y29320

Self-heal Daemon on localhostN/AY29337

NFS Server on w-ostack03.sys.bjdt.net2049Y17638

Self-heal Daemon on w-ostack03.sys.bjdt.netN/AY30385

Task Status of Volume tank

------------------------------------------------------------------------------

There are no active volume tasks

故障log：

[2016-04-08 03:24:33.909878] I [graph.c:269:gf_add_cmdline_options] 0-tank-server: adding option 'listen-port' for volume 'tank-server' with value '49152'

[2016-04-08 03:24:33.909921] I [graph.c:269:gf_add_cmdline_options] 0-tank-posix: adding option 'glusterd-uuid' for volume 'tank-posix' with value '6b2cfe95-1eb1-4510-b7db-af34ba73162c'

[2016-04-08 03:24:33.911030] I [rpcsvc.c:2142:rpcsvc_set_outstanding_rpc_limit] 0-rpc-service: Configured rpc.outstanding-rpc-limit with value 64

[2016-04-08 03:24:33.911090] W [options.c:898:xl_opt_validate] 0-tank-server: option 'listen-port' is deprecated, preferred is 'transport.socket.listen-port', continuing with correction

[2016-04-08 03:24:33.912278] E [posix.c:5632:init] 0-tank-posix: Extended attribute trusted.glusterfs.volume-id is absent

[2016-04-08 03:24:33.912297] E [xlator.c:425:xlator_init] 0-tank-posix: Initialization of volume 'tank-posix' failed, review your volfile again

[2016-04-08 03:24:33.912306] E [graph.c:322:glusterfs_graph_init] 0-tank-posix: initializing translator failed

[2016-04-08 03:24:33.912315] E [graph.c:525:glusterfs_graph_activate] 0-graph: init failed

[2016-04-08 03:24:33.912689] W [glusterfsd.c:1211:cleanup_and_exit] (--> 0-: received signum (0), shutting down

故障分析：

# getfattr -dm . -e hex tank

查看對應brick目錄，缺少擴展屬性。

解決方案：

擴展屬性很多，這里只需要手動添加trusted.glusterfs.volume-id屬性即可。

實例操作如下：

setfattr -n trusted.glusterfs.volume-id -v 0xd810be517a524864bfa7e94fd52c4dbc tank

然后重啟服務：

systemctl restart glusterd.service   # centos 7上操作命令

service glusterd restart

故障解決，然后如果是復制卷，可以執行heal命令，恢復未數據。

gluster volume heal tank full

感謝各位的閱讀，以上就是“gluster brick進程啟動失敗怎么處理”的內容了，經過本文的學習后，相信大家對gluster brick進程啟動失敗怎么處理這一問題有了更深刻的體會，具體使用情況還需要大家實踐驗證。這里是億速云，小編將為大家推送更多相關知識點的文章，歡迎關注！