[Bugs] [Bug 1331934] glusterd restart is failing if volume brick is down due to underlying FS crash.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1331934



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14124 committed in release-3.7 by Jeff Darcy
(jdarcy at redhat.com) 
------
commit 45f6b416be0a8daeca9752910a332201bc17d851
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Tue Apr 26 15:27:43 2016 +0530

    glusterd: persist brickinfo->real_path

    Backport of http://review.gluster.org/14075

    Since real_path was not persisted and gets constructed at every glusterd
    restart, glusterd will fail to come up if one of the brick's underlying
file
    system is crashed.

    Solution is to construct real_path only once and get it persisted.

    Change-Id: I97abc30372c1ffbbb2d43b716d7af09172147b47
    BUG: 1331934
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/14075
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kaushal M <kaushal at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-on: http://review.gluster.org/14124
    Reviewed-by: Jeff Darcy <jdarcy 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=PH5i23LI7q&a=cc_unsubscribe