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

bugzilla at redhat.com bugzilla at redhat.com
Sat Aug 4 06:11:58 UTC 2018


--- Comment #1 from Mohit Agrawal <moagrawa at redhat.com> ---

Brick is not coming up after reboot because of fsid comparison failing at the
time of start brick. The fsid comparison is failed because fsid is changed
reboot the node.To resolve the same compare volume_id xattr with saved
volume_uid before start/attach a brick.volume_id is populated on a brick_root
path at the time of creating a volume and same volume_id is stored on the
backend by glusterd.

Mohit Agrawal

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=7jdnC1W0Qw&a=cc_unsubscribe

More information about the Bugs mailing list