Brick down and Gluster volume fails to 'force' start
Issue
- After a system crash of a gluster node, one of the brick of that node appears offline
-
command gluster volume heal info shows transport endpoint not connected as here:
gluster volume heal data info Brick rhhi-1.lab.roskosb.info:/gluster_bricks/data/data Status: Transport endpoint is not connected ------------> error Number of entries: -
-
gluster volume is unresponsive to
gluster volume start <volume_name> force
Environment
- Red Hat Gluster Storage 3.5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.