Shulou(Shulou.com)06/01 Report--

This article mainly explains the "gluster brick process startup failure how to deal with", the article explains the content is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in depth, together to study and learn "how to deal with gluster brick process startup failure" bar!

Environment description:

Replication volume, under centos 7, gluster version 3.6.7

Failure phenomenon:

# 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

Fault log:

I [graph.c:269:gf_add_cmdline_options] 0-tank-server: adding option 'listen-port' for volume' tank-server' with value '49152'

I [graph.c:269:gf_add_cmdline_options] 0-tank-posix: adding option 'glusterd-uuid' for volume' tank-posix' with value '6b2cfe95-1eb1-4510Mub b7dblusaf34ba73162c'

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

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 03VOR 24VOV 33.912278] E [posix.c:5632:init] 0-tank-posix: Extended attribute trusted.glusterfs.volume-id is absent

] E [xlator.c:425:xlator_init] 0-tank-posix: Initialization of volume 'tank-posix' failed, review your volfile again

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

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

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

Fault analysis:

# getfattr-dm. -e hex tank

Check the corresponding brick directory and the extension attribute is missing.

Solution:

There are a lot of extended attributes, and here you just need to add the trusted.glusterfs.volume-id attribute manually.

The operation of the example is as follows:

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

Then restart the service:

Operation commands on systemctl restart glusterd.service # centos 7

Service glusterd restart

"the problem is resolved, and then if you are replicating the volume, you can execute the heal command to recover the missing data."

Gluster volume heal tank full

Thank you for your reading, the above is the content of "how to deal with gluster brick process startup failure". After the study of this article, I believe you have a deeper understanding of how to deal with gluster brick process startup failure, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.