[Bugs] [Bug 1686396] New: ls and rm run on contents of same directory from a single mount point results in ENOENT errors

bugzilla at redhat.com bugzilla at redhat.com
Thu Mar 7 11:20:40 UTC 2019


            Bug ID: 1686396
           Summary: ls and rm run on contents of same directory from a
                    single mount point results in ENOENT errors
           Product: GlusterFS
           Version: 4.1
            Status: NEW
         Component: core
          Assignee: bugs at gluster.org
          Reporter: rgowdapp at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community

Description of problem:

This bug was reported by Nithya.

Create a pure replicate volume and enable the following options:
Volume Name: xvol
Type: Replicate
Volume ID: 095d6083-ea82-4ec9-a3a9-498fbd5f8dbe
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Options Reconfigured:
server.event-threads: 4
client.event-threads: 4
performance.parallel-readdir: on
performance.readdir-ahead: on
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off

Fuse mount using:
mount -t glusterfs -o lru-limit=500 -s /mnt/g1
mkdir /mnt/g1/dirdd

>From terminal 1:
cd /mnt/g1/dirdd
while (true); do ls -lR dirdd; done

>From terminal 2:
while true; do dd if=/dev/urandom of=/mnt/g1/dirdd/1G.file bs=1M count=1; rm -f
/mnt/g1/dirdd/1G.file; done

With performance.parallel-readdir on, ls runs into ESTALE errors. With
performance.parallel-readdir off, no errors are seen.

Note that both ls and rm are running on same mount point.

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

How reproducible:

Steps to Reproduce:

Actual results:
ls runs into ESTALE errors

Expected results:
ls shouldn't run into ESTALE errors

Additional info:

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

More information about the Bugs mailing list