[Bugs] [Bug 1175745] AFR + Snapshot : Read operation on file in split-brain is successful in USS

[bugzilla at redhat.com]

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

Pranith Kumar K <pkarampu at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
                 CC|                            |pkarampu at redhat.com
         Resolution|---                         |NEXTRELEASE
        Last Closed|                            |2016-08-23 08:32:39



--- Comment #4 from Pranith Kumar K <pkarampu at redhat.com> ---
commit 6b83a658ede66ebbb0983f1e4a326fd12cc91c34
Author: Rajesh Joseph <rjoseph at redhat.com>
Date:   Mon Dec 8 14:25:22 2014 +0530

    gfapi: new inode created in glfs_resolve_component even if inode is in
inode table

    problem: USS allows split-brain file to be accessed while main volume
             gives I/O error.

    cause:
            AFR detects split-brain on lookup. It stores this information in
            inode context. open and readv fop checks this flag from inode
context.
            open and readv fop fails if split-brain flag is set for the file.

            USS uses gfapi to access snapshot volume. During open call
            gfapi internally calls glfs_resolve_component.
glfs_resolve_component
            generates a new inode even if inode is present for the file.
            Because of which afr_lookup acts on a new inode which does not
            contain the split-brain flag.

    Bug: 1171615

    Change-Id: I1b4fddf4bd3c734a319ecfae804a3439866d157c
    Signed-off-by: Rajesh Joseph <rjoseph at redhat.com>
    Reviewed-on: http://review.gluster.org/9253
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika at redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur at redhat.com>
    Reviewed-by: Poornima G <pgurusid at redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.