[Bugs] [Bug 1801615] New: FUSE mount : touch exact the same file right after rm FAIL

[bugzilla at redhat.com]

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

            Bug ID: 1801615
           Summary: FUSE mount : touch exact the same file right after rm
                    FAIL
           Product: GlusterFS
           Version: mainline
                OS: Linux
            Status: NEW
         Component: fuse
          Assignee: bugs at gluster.org
          Reporter: Cliff.Lu at infortrend.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
Touch exact the same file right after rm FAIL
We're using v4.1.8 and found this issue in v4.1.8.
But it could also be duplicate with master branch.

I've checked some log and code trace, 
It seems create/lookup fail before FUSE_FORGET for unlink comes.
I thought it shouldn't create/lookup as the same nodeid?

Version-Release number of selected component (if applicable):
tag/v4.1.8, branch/master

How reproducible:
It happens all the time if no other delays between sys call.
I've try 1000-times repeat, with 184 touch fail.
(The first time rm-touch almost 100% failed)

Steps to Reproduce:
1.
Create any type of volume(EC/Rep/Distribute)
mount with FUSE.
2.
rm aaa
touch aaa
with no other delay between two commands. (I've tried both shell, python)
3.
check touch fail

Actual results:
In master
touch: setting times of ‘/mnt/test/aaa’: Stale file handle
In v4.1.8
touch: setting times of ‘/mnt/test/aaa’: No such file or directory
file aaa not exist.

Expected results:
touch success
file aaa exist

Additional info:
OS - CentOS7.4

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