|
Found it.
Filesystem on 1 of the nodes was corrupt. Removing that brick, fixing the filesytem and adding the brick again solved the problem. From: Graaf, Max de
Sent: Friday, January 25, 2019 1:32:41 PM To: Gluster-users Subject: Brick stays offline after update from 4.1.6-1.el7 to 4.1.7-1.el7
We have 2 nodes running CentOS 7.3. Running just fine with glusterfs 4.1.6-1.el7. This morning update both to 4.1.7-1.el7 and the only brick configured stays offline.
gluster peer status show no problems:
Number of Peers: 1
Hostname: 10.159.241.35
Uuid: 7453dbec-44fb-4e57-9471-6e653d287d3b
State: Peer in Cluster (Connected)
Number of Peers: 1
Hostname: 10.159.241.3
Uuid: 8f0e75bd-c782-4d21-aaf3-2d8a27e8a714
State: Peer in Cluster (Connected)
gluster volume status show the bricks offline:
Status of volume: gst
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick grpprdaalcgst01.cloudprod.local:/apps
/glusterfs-gst/gst 49152 0 Y 8827
Brick grpprdapdcgst01.cloudprod.local:/apps
/glusterfs-gst/gst N/A N/A N N/A
Self-heal Daemon on localhost N/A N/A Y 8818
Self-heal Daemon on grpprdapdcgst01.cloudpr
od.local N/A N/A Y 28111
Task Status of Volume gst
------------------------------------------------------------------------------
There are no active volume tasks
Status of volume: gst
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick grpprdaalcgst01.cloudprod.local:/apps
/glusterfs-gst/gst 49152 0 Y 8827
Brick grpprdapdcgst01.cloudprod.local:/apps
/glusterfs-gst/gst N/A N/A N N/A
Self-heal Daemon on localhost N/A N/A Y 28111
Self-heal Daemon on 10.159.241.3 N/A N/A Y 8818
Task Status of Volume gst
------------------------------------------------------------------------------
There are no active volume tasks
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
