Troubleshooting
Problem
Gluster bricks down over multiple volumes. Running gluster volume status shows many bricks are down across multiple nodes.
Symptom
Gluster bricks down over multiple volumes. Running gluster volume status shows many bricks are down across multiple nodes.
Cause
Gluster bricks down over multiple volumes. Running gluster volume status shows many bricks are down across multiple nodes.
Environment
WSL 1.2.3.1 on Linux
Diagnosing The Problem
Run the command: gluster volume status
Resolving The Problem
First of all verify that the nodes have not run out of space using the df -h command. If it is not a space issue then use the following method:
1) ensure all pool members are online : gluster pool status (should show all as connected)
2) Check the peers status: gluster peer status (should show all as connected)
2) Check the peers status: gluster peer status (should show all as connected)
If those look good just run the following:
gluster volume list | awk '{system("gluster volume stop "$1 " force --mode=script")}'
gluster volume list | awk '{system("gluster volume start "$1 " force")}'
gluster volume list | awk '{system("gluster volume start "$1 " force")}'
If they stop and start then issue is resolved.
Quick check: gluster volume status ' N '
If any lines are returned then check if it is bricks or agents by stepping through
gluster volume status
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHGWL","label":"IBM Watson Studio Local"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"1.2.3.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
30 December 2019
UID
ibm10958793