Brick is offline due to missing extended attribute trusted.glusterfs.volume-id

Solution In Progress - Updated -

Issue

When a server is rebooted, the brick was not mounted resulting in the failure of the brick to come online.

A 'gluster volume start force' will report success but sometime later, the brick will go offline.

Environment

glusterfs 3.*

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