Brick down and Gluster volume fails to 'force' start

Solution Verified - Updated -


  • 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
                   Status: Transport endpoint is not connected ------------> error
                   Number of entries: -  
  • gluster volume is unresponsive to gluster volume start <volume_name> force


  • Red Hat Gluster Storage 3.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content