[Bugs] [Bug 1462636] Use of force with volume start, creates brick directory even it is not present

bugzilla at redhat.com bugzilla at redhat.com
Mon Jun 19 15:48:14 UTC 2017


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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17562 committed in release-3.11 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit df807e0ae37e57dd1ffd7ac2ac8e177d44877da0
Author: Ravishankar N <ravishankar at redhat.com>
Date:   Thu Jun 15 15:36:07 2017 +0530

    index: Do not proceed with init if brick is not mounted

    ..or else when a volume start force is given, we end up creating
    /brick-path/.glusterfs/indices folder and various subdirs under it and
    eventually starting the brick process.

    As a part of this patch, glusterd_get_index_basepath() is added in
    glusterd, who will then use it to create the basepath during
    volume-create, add-brick, replace-brick and reset-brick. It also uses this
    function to set the 'index-base' xlator option for the index translator.

    > Reviewed-on: https://review.gluster.org/17426
    > Smoke: Gluster Build System <jenkins at build.gluster.org>
    > NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    > Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    (cherry picked from commit b58a15948fb3fc37b6c0b70171482f50ed957f42)

    Change-Id: Id018cf3cb6f1e2e35b5c4cf438d1e939025cb0fc
    BUG: 1462636
    Signed-off-by: Ravishankar N <ravishankar at redhat.com>
    Reviewed-on: https://review.gluster.org/17562
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster 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=2i3wUT55ex&a=cc_unsubscribe


More information about the Bugs mailing list