Environment Description:
Copy volume, CentOS 7, gluster version 3.6.7
Failure phenomena:
# 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/A
NFS Server on localhost2049Y29320
Self-heal Daemon on localhostn/a Y 29337
NFS Server on w-ostack03.sys.bjdt.net2049Y17638
Self-heal Daemon on w-ostack03.sys.bjdt.netn/a Y 30385
Task Status of Volume tank
------------------------------------------------------------------------------
There is no active volume tasks
Fault 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 ' 49 152 '
[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 ' 6b 2cfe95-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
Fault Analysis:
# GETFATTR-DM. -E hex Tank
View the corresponding brick directory, missing extended attributes.
Solution:
There are many extended properties, and you only need to add the Trusted.glusterfs.volume-id property manually.
The instance operations are as follows:
Setfattr-n trusted.glusterfs.volume-id-v 0XD810BE517A524864BFA7E94FD52C4DBC Tank
Then restart the service:
Systemctl Restart Glusterd.service # CentOS 7 Operation command
Service Glusterd Restart
troubleshooting, and then if the volume is replicated, you can execute the heal command to recover the data.
Gluster Volume Heal Tank full
Perfect solution.
This article is from the "Members Doukua" blog, make sure to keep this source http://dangzhiqiang.blog.51cto.com/7961271/1761677
Gluster brick Process Start failure handling method