REVIEW: http://review.gluster.org/13066 (cluster/ec: Get size and config for invalid inode) posted (#1) for review on release-3.7 by Ashish Pandey (aspandey)

COMMIT: http://review.gluster.org/13066 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit b6b68fb15efc614e3718cbc42c6231ee9ac2593b
Author: Ashish Pandey <aspandey>
Date:   Mon Dec 21 16:04:20 2015 +0530

    cluster/ec: Get size and config for invalid inode
    
    Problem:
    After creating an inode and before linking it
    to inode table, if there is a request to setattr
    for that file, it fails and leads to crash.
    Before linking inode to inode table ia_type is IA_INVAL
    which will casue have_size and have_config as zero.
    
    Solution:
    Check and get size and config if an inode is invalid
    
    master-
    http://review.gluster.org/#/c/13039/
    
    Change-Id: I0c0e564940b1b9f351369a76ab14f6b4aa81f23b
    BUG: 1293224
    Signed-off-by: Ashish Pandey <aspandey>
    Reviewed-on: http://review.gluster.org/13066
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>

REVIEW: http://review.gluster.org/13239 (cluster/ec: Handle non-existent config xattr for non regular files) posted (#1) for review on release-3.7 by Xavier Hernandez (xhernandez)

REVIEW: http://review.gluster.org/13239 (cluster/ec: Handle non-existent config xattr for non regular files) posted (#2) for review on release-3.7 by Xavier Hernandez (xhernandez)

REVIEW: http://review.gluster.org/13239 (cluster/ec: Handle non-existent config xattr for non regular files) posted (#3) for review on release-3.7 by Xavier Hernandez (xhernandez)

COMMIT: http://review.gluster.org/13239 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 626534e94b4ac07b99a2cc479f004935664a09a2
Author: Xavier Hernandez <xhernandez>
Date:   Thu Jan 14 09:36:33 2016 +0100

    cluster/ec: Handle non-existent config xattr for non regular files
    
    Since we now try to get the 'trusted.ec.config' xattr for inodes of
    type IA_INVAL (these inodes will be set to some valid type later),
    if that inode corresponds to a non regular file, the xattr won't
    exist and we will handle this as an error when it's not.
    
    This patch solves the problem by only considering errors for inodes
    that are already known to be regular files.
    
    > Change-Id: Id72f314e209459236d75cf087fc51e09943756b4
    > BUG: 1293223
    > Signed-off-by: Xavier Hernandez <xhernandez>
    > Reviewed-on: http://review.gluster.org/13238
    
    Change-Id: I48a475ce889607e9b909f699b5d7f75b0657cb22
    BUG: 1293224
    Signed-off-by: Xavier Hernandez <xhernandez>
    Reviewed-on: http://review.gluster.org/13239
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>

REVIEW: http://review.gluster.org/13447 (cluster/ec: Fix invalid config check for directories) posted (#1) for review on release-3.7 by Xavier Hernandez (xhernandez)

COMMIT: http://review.gluster.org/13447 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 6662b0a9cf19fdbe75e67f70a98df44d4852467c
Author: Xavier Hernandez <xhernandez>
Date:   Mon Feb 15 10:59:29 2016 +0100

    cluster/ec: Fix invalid config check for directories
    
    The trusted.ec.config xattr is not defined for directories. However
    sometimes it could be requested because the inode type of a directory
    can temporarily be IA_INVAL.
    
    Requesting such xattr using the xattrop fop when it doesn't exist,
    returns a config value full of 0's, which is invalid and caused some
    fops to fail.
    
    This patch filters out this case by ignoring config xattr == 0.
    
    > Change-Id: Ied51c35b313ea8c3eeae27812f9bae61d3808e92
    > Reviewed-on: http://review.gluster.org/13446
    > BUG: 1293223
    > Signed-off-by: Xavier Hernandez <xhernandez>
    
    Change-Id: I42d06119d8f51c34ddb910380af7acd670f6244e
    BUG: 1293224
    Signed-off-by: Xavier Hernandez <xhernandez>
    Reviewed-on: http://review.gluster.org/13447
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Ashish Pandey <aspandey>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

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.9, please open a new bug report.

glusterfs-3.7.9 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] https://www.gluster.org/pipermail/gluster-users/2016-March/025922.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

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.7, please open a new bug report.

glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user