[Bugs] [Bug 1313921] Incorrect file size on mount if stat is served from the arbiter brick.

bugzilla at redhat.com bugzilla at redhat.com
Sat Mar 5 01:29:05 UTC 2016


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



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13582 committed in release-3.7 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit ad0b1253b9d74797620c493184818685c024f17c
Author: Ravishankar N <ravishankar at redhat.com>
Date:   Mon Feb 29 05:16:50 2016 +0000

    afr: do not set arbiter as a readable subvol in inode context

    Backport-of: http://review.gluster.org/#/c/13539/

    Problem:
    If afr_lookup_done() or afr_read_subvol_select_by_policy() chooses the
    arbiter brick to serve the stat() data, file size will be reported as
    zero from the mount, despite other data bricks being available. This can
    break programs like tar which use the stat info to decide how much to read.

    Fix:
    In the inode-context, mark arbiter as a non-readable subvol for both
    data and metadata.

    It it to be noted that by making this fix, we are *not* going to serve
    metadata FOPS anymore from the arbiter brick despite the brick storing
    the metadata. It makes sense to do this because the ever increasing
    over-loaded FOPs (getxattr returning stat data etc.) and compound FOPS
    in gluster will otherwise make it difficult to add checks in code to
    handle corner cases.

    Change-Id: Ic60b25d77fd05e0897481b7fcb3716d4f2101001
    BUG: 1313921
    Signed-off-by: Ravishankar N <ravishankar at redhat.com>
    Reported-by: Mat Clayton <mat at mixcloud.com>
    Reviewed-on: http://review.gluster.org/13582
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu 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=oHAjCjY5MP&a=cc_unsubscribe


More information about the Bugs mailing list