Bug 1171615 - AFR + Snapshot : Read operation on file in split-brain is successful in USS
Summary: AFR + Snapshot : Read operation on file in split-brain is successful in USS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: pre-release
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: rjoseph
QA Contact:
URL:
Whiteboard: USS
Depends On:
Blocks: 1169916 1175745
TreeView+ depends on / blocked
 
Reported: 2014-12-08 08:53 UTC by rjoseph
Modified: 2015-05-14 17:45 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.7.0
Doc Type: Bug Fix
Doc Text:
Clone Of: 1169916
: 1175745 1179659 (view as bug list)
Environment:
Last Closed: 2015-05-14 17:28:40 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-12-08 09:21:23 UTC
REVIEW: http://review.gluster.org/9253 (gfapi: new inode created in glfs_resolve_component even if inode is in inode table) posted (#1) for review on master by Rajesh Joseph (rjoseph)

Comment 2 Anand Avati 2014-12-08 15:32:50 UTC
COMMIT: http://review.gluster.org/9253 committed in master by Niels de Vos (ndevos) 
------
commit 6b83a658ede66ebbb0983f1e4a326fd12cc91c34
Author: Rajesh Joseph <rjoseph>
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>
    Reviewed-on: http://review.gluster.org/9253
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika>
    Reviewed-by: Raghavendra Talur <rtalur>
    Reviewed-by: Poornima G <pgurusid>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>

Comment 3 Anand Avati 2015-01-07 11:53:12 UTC
REVIEW: http://review.gluster.org/9343 (gfapi: new inode created in glfs_resolve_component even if inode is in inode table) posted (#2) for review on release-3.6 by Raghavendra Talur (rtalur)

Comment 4 Niels de Vos 2015-05-14 17:28:40 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:35:45 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:38:07 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:45:14 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.