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

bugzilla at redhat.com bugzilla at redhat.com
Fri Apr 29 16:17:26 UTC 2016


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



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

    glusterd: persist brickinfo->real_path

    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: 1330481
    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>

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


More information about the Bugs mailing list