Why glusterfsd failed to start with "discovered already-running brick /path/to/brick" in glusterd.log

Solution Verified - Updated -

Issue

  • gluster volume start <VOLUME> force failed to start a brick with following message in glusterd.log.
[2021-10-20 04:03:11.247663] I [glusterd-utils.c:6235:glusterd_brick_start] 0-management: discovered already-running brick /path/to/brick
[2021-10-20 04:03:11.247713] I [MSGID: 106143] [glusterd-pmap.c:282:pmap_registry_bind] 0-pmap: adding brick /path/to/brick on port 49203

Environment

  • 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