glusterfsd process can not start because volume-id in brick is lost.

Solution In Progress - Updated -

Issue

  • glusterfsd process can not start because volume-id in brick is lost.

    For example,

    E [posix.c:5075:init] 0-asgpcsvol01-posix: Extended attribute trusted.glusterfs.volume-id is absent
    

Environment

  • Red Hat Storage Server 2.1
  • Red Hat Storage Server 3.0.3 or earlier

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.