Bug 762683 (GLUSTER-951)

Summary: Unwind if inode_ctx fails in all FOPS
Product: [Community] GlusterFS Reporter: Pavan Vilas Sondur <pavan>
Component: protocolAssignee: Pavan Vilas Sondur <pavan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 3.0.4CC: anush, gluster-bugs, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pavan Vilas Sondur 2010-05-26 14:22:10 UTC
Need to return and UNWIND if inode_ctx fails in any of the FOPs in client-protocol

Comment 1 Anand Avati 2010-05-27 12:18:27 UTC
PATCH: http://patches.gluster.com/patch/3327 in master (protocol/client: Unwind with error if getting remote inode number fails.)

Comment 2 Anand Avati 2010-05-27 12:18:34 UTC
PATCH: http://patches.gluster.com/patch/3326 in release-3.0 (protocol/client: Unwind with error if getting remote inode number fails.)

Comment 3 Anush Shetty 2010-06-17 08:40:31 UTC
In 3.0.5rc6

[root@RHEL-Server client2]# mkdir kernel5
[root@RHEL-Server client2]# cd kernel5
[root@RHEL-Server kernel5]# touch dot
[root@RHEL-Server kernel5]# ln -s dot do3
[root@RHEL-Server kernel5]# ls
do3  dot
[root@RHEL-Server kernel5]# ls dot
dot
[root@RHEL-Server kernel5]# ls do3
ls: do3: Invalid argument

ls -l works

Comment 4 Anush Shetty 2010-06-17 10:41:04 UTC
Observed this behaviour only on stripe. Hence closing this bug and move it to a new bug: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1006