[Bugs] [Bug 1612418] Brick not coming up on a volume after rebooting the node

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 10 17:52:07 UTC 2018


Worker Ant <bugzilla-bot at gluster.org> changed:

           What    |Removed                     |Added
             Status|POST                        |MODIFIED

--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/20638 committed in master by "Atin
Mukherjee" <amukherj at redhat.com> with a commit message- glusterd: Compare
volume_id before start/attach a brick

Problem: After reboot a node brick is not coming up because
         fsid comparison is failed before start a brick

Solution: Instead of comparing fsid compare volume_id to
          resolve the same because fsid is changed after
          reboot a node but volume_id persist as a xattr
          on brick_root path at the time of creating a volume.

Change-Id: Ic289aab1b4ebfd83bbcae8438fee26ae61a0fff4
fixes: bz#1612418
Signed-off-by: Mohit Agrawal <moagrawal at redhat.com>

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=U4goKA8CVM&a=cc_unsubscribe

More information about the Bugs mailing list