[Bugs] [Bug 1421653] New: dht_setxattr returns EINVAL when a file is deleted during the FOP

[bugzilla at redhat.com]

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

            Bug ID: 1421653
           Summary: dht_setxattr returns EINVAL when a file is deleted
                    during the FOP
           Product: GlusterFS
           Version: mainline
         Component: distribute
          Assignee: bugs at gluster.org
          Reporter: nbalacha at redhat.com
                CC: bugs at gluster.org



Description of problem:

dht_setxattr returns EINVAL when a file is deleted after the FOP hits
dht_setxattr.



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


How reproducible:
Consistently


Steps to Reproduce:
1. Create a dist-rep volume (I used a 4x2)
2. Fuse mount the volume on 2 different mount points (/mnt/g1 and /mnt/g2)
3. gdb into the mount process for /mnt/g2 and set a breakpoint on dht_setxattr
4. From /mnt/g1, touch file1
5. From /mnt/g2, set an xattr on file1. This will hit the breakpoint set in (3)
6. From /mnt/g1, rm file1
7. Continue in gdb


Actual results:
[root at rhgs313-6 g2]# setfattr -n trusted.test.yahh -v "testing 1 2 3..." file1 
setfattr: file1: Invalid argument



Expected results:
[root at rhgs313-6 g2]# setfattr -n trusted.test.yahh -v "testing 1 2 3..." file1
setfattr: file1: No such file or directory


Additional info:

The same issue shows up in dht_removexattr as well. (Repeat the test steps with
the breakpoint in dht_removexattr and "setxfattr -x" )

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