Bug 1024666 - setfattr fails on directories when gfid-access xlator is loaded
Summary: setfattr fails on directories when gfid-access xlator is loaded
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-30 08:13 UTC by Pranith Kumar K
Modified: 2014-04-17 11:50 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.5.0
Clone Of:
Environment:
Last Closed: 2014-04-17 11:50:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Pranith Kumar K 2013-10-30 08:13:34 UTC
Description of problem:

gfid and inode are changed in ga_virtual_lookup_cbk. Because of these changes, operations on the file are failing with EINVAL because in setxattr call of gfid-access xlator it does not do the reverse equivalent of what happens in ga_virtual_lookup_cbk so dht-layout-set happens on one inode but setxattr is sent on some other inode.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. create a directory hierarchy with some depth.
2. for each gfid of these directories perform a setfattr
3. Some of the commands fail with Invalid Argument error.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2013-10-30 08:14:28 UTC
REVIEW: http://review.gluster.org/6194 (features/gfid-access: Handle inode remap when parent inode is NULL) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2013-10-31 10:53:31 UTC
COMMIT: http://review.gluster.org/6194 committed in master by Vijay Bellur (vbellur) 
------
commit 301ecf4798ae5271b2155efee92e5d1ad734b05b
Author: Pranith Kumar K <pkarampu>
Date:   Wed Oct 30 11:57:01 2013 +0530

    features/gfid-access: Handle inode remap when parent inode is NULL
    
    Change-Id: Ic3f9d30d75df0bbbdf8fe28446fabe62d90fa854
    BUG: 1024666
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/6194
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Amar Tumballi <amarts>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2014-04-17 11:50:11 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.5.0, please reopen this bug report.

glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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/6137
[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.