Description of problem: ----------------------- EC (4+2) volume mounted via FUSE on 6 clients,parallel readdir enabled. ANY CLIENT : touch a CLIENT 1 : mv a b ----> PASSED CLIENT 2 : mv a c -----> PASSED CLIENT 3 : mv a d ------> PASSED I see b,c and d on my mount point : [root@gqac015 gluster-mount]# ls 1 2 3 4 5 b b c c d d [root@gqac015 gluster-mount]# I could not repro it without parallel readdir though.I get this on other clients : [root@gqac006 gluster-mount]# mv a b mv: cannot move ‘a’ to ‘b’: No such file or directory Version-Release number of selected component (if applicable): ------------------------------------------------------------- glusterfs-3.8.4-20.el7rhgs.x86_64 How reproducible: ----------------- 100% Steps to Reproduce: ------------------- Broadcast rename command with a different name on different clients. *Vol Info* : [root@gqas013 ~]# gluster v info Volume Name: butcher Type: Distributed-Disperse Volume ID: 55902003-7ea9-4f58-987d-63c6c759a385 Status: Started Snapshot Count: 0 Number of Bricks: 12 x (4 + 2) = 72 Transport-type: tcp Bricks: Brick1: gqas013.sbu.lab.eng.bos.redhat.com:/bricks1/brick Brick2: gqas005.sbu.lab.eng.bos.redhat.com:/bricks1/brick Brick3: gqas006.sbu.lab.eng.bos.redhat.com:/bricks1/brick Brick4: gqas008.sbu.lab.eng.bos.redhat.com:/bricks1/brick Brick5: gqas014.sbu.lab.eng.bos.redhat.com:/bricks1/brick Brick6: gqas015.sbu.lab.eng.bos.redhat.com:/bricks1/brick Brick7: gqas013.sbu.lab.eng.bos.redhat.com:/bricks2/brick Brick8: gqas005.sbu.lab.eng.bos.redhat.com:/bricks2/brick Brick9: gqas006.sbu.lab.eng.bos.redhat.com:/bricks2/brick Brick10: gqas008.sbu.lab.eng.bos.redhat.com:/bricks2/brick Brick11: gqas014.sbu.lab.eng.bos.redhat.com:/bricks2/brick Brick12: gqas015.sbu.lab.eng.bos.redhat.com:/bricks2/brick Brick13: gqas013.sbu.lab.eng.bos.redhat.com:/bricks3/brick Brick14: gqas005.sbu.lab.eng.bos.redhat.com:/bricks3/brick Brick15: gqas006.sbu.lab.eng.bos.redhat.com:/bricks3/brick Brick16: gqas008.sbu.lab.eng.bos.redhat.com:/bricks3/brick Brick17: gqas014.sbu.lab.eng.bos.redhat.com:/bricks3/brick Brick18: gqas015.sbu.lab.eng.bos.redhat.com:/bricks3/brick Brick19: gqas013.sbu.lab.eng.bos.redhat.com:/bricks4/brick Brick20: gqas005.sbu.lab.eng.bos.redhat.com:/bricks4/brick Brick21: gqas006.sbu.lab.eng.bos.redhat.com:/bricks4/brick Brick22: gqas008.sbu.lab.eng.bos.redhat.com:/bricks4/brick Brick23: gqas014.sbu.lab.eng.bos.redhat.com:/bricks4/brick Brick24: gqas015.sbu.lab.eng.bos.redhat.com:/bricks4/brick Brick25: gqas013.sbu.lab.eng.bos.redhat.com:/bricks5/brick Brick26: gqas005.sbu.lab.eng.bos.redhat.com:/bricks5/brick Brick27: gqas006.sbu.lab.eng.bos.redhat.com:/bricks5/brick Brick28: gqas008.sbu.lab.eng.bos.redhat.com:/bricks5/brick Brick29: gqas014.sbu.lab.eng.bos.redhat.com:/bricks5/brick Brick30: gqas015.sbu.lab.eng.bos.redhat.com:/bricks5/brick Brick31: gqas013.sbu.lab.eng.bos.redhat.com:/bricks6/brick Brick32: gqas005.sbu.lab.eng.bos.redhat.com:/bricks6/brick Brick33: gqas006.sbu.lab.eng.bos.redhat.com:/bricks6/brick Brick34: gqas008.sbu.lab.eng.bos.redhat.com:/bricks6/brick Brick35: gqas014.sbu.lab.eng.bos.redhat.com:/bricks6/brick Brick36: gqas015.sbu.lab.eng.bos.redhat.com:/bricks6/brick Brick37: gqas013.sbu.lab.eng.bos.redhat.com:/bricks7/brick Brick38: gqas005.sbu.lab.eng.bos.redhat.com:/bricks7/brick Brick39: gqas006.sbu.lab.eng.bos.redhat.com:/bricks7/brick Brick40: gqas008.sbu.lab.eng.bos.redhat.com:/bricks7/brick Brick41: gqas014.sbu.lab.eng.bos.redhat.com:/bricks7/brick Brick42: gqas015.sbu.lab.eng.bos.redhat.com:/bricks7/brick Brick43: gqas013.sbu.lab.eng.bos.redhat.com:/bricks8/brick Brick44: gqas005.sbu.lab.eng.bos.redhat.com:/bricks8/brick Brick45: gqas006.sbu.lab.eng.bos.redhat.com:/bricks8/brick Brick46: gqas008.sbu.lab.eng.bos.redhat.com:/bricks8/brick Brick47: gqas014.sbu.lab.eng.bos.redhat.com:/bricks8/brick Brick48: gqas015.sbu.lab.eng.bos.redhat.com:/bricks8/brick Brick49: gqas013.sbu.lab.eng.bos.redhat.com:/bricks9/brick Brick50: gqas005.sbu.lab.eng.bos.redhat.com:/bricks9/brick Brick51: gqas006.sbu.lab.eng.bos.redhat.com:/bricks9/brick Brick52: gqas008.sbu.lab.eng.bos.redhat.com:/bricks9/brick Brick53: gqas014.sbu.lab.eng.bos.redhat.com:/bricks9/brick Brick54: gqas015.sbu.lab.eng.bos.redhat.com:/bricks9/brick Brick55: gqas013.sbu.lab.eng.bos.redhat.com:/bricks10/brick Brick56: gqas005.sbu.lab.eng.bos.redhat.com:/bricks10/brick Brick57: gqas006.sbu.lab.eng.bos.redhat.com:/bricks10/brick Brick58: gqas008.sbu.lab.eng.bos.redhat.com:/bricks10/brick Brick59: gqas014.sbu.lab.eng.bos.redhat.com:/bricks10/brick Brick60: gqas015.sbu.lab.eng.bos.redhat.com:/bricks10/brick Brick61: gqas013.sbu.lab.eng.bos.redhat.com:/bricks11/brick Brick62: gqas005.sbu.lab.eng.bos.redhat.com:/bricks11/brick Brick63: gqas006.sbu.lab.eng.bos.redhat.com:/bricks11/brick Brick64: gqas008.sbu.lab.eng.bos.redhat.com:/bricks11/brick Brick65: gqas014.sbu.lab.eng.bos.redhat.com:/bricks11/brick Brick66: gqas015.sbu.lab.eng.bos.redhat.com:/bricks11/brick Brick67: gqas013.sbu.lab.eng.bos.redhat.com:/bricks12/brick Brick68: gqas005.sbu.lab.eng.bos.redhat.com:/bricks12/brick Brick69: gqas006.sbu.lab.eng.bos.redhat.com:/bricks12/brick Brick70: gqas008.sbu.lab.eng.bos.redhat.com:/bricks12/brick Brick71: gqas014.sbu.lab.eng.bos.redhat.com:/bricks12/brick Brick72: gqas015.sbu.lab.eng.bos.redhat.com:/bricks12/brick Options Reconfigured: performance.parallel-readdir: on transport.address-family: inet nfs.disable: on features.cache-invalidation: on features.cache-invalidation-timeout: 600 performance.stat-prefetch: on performance.cache-invalidation: on performance.md-cache-timeout: 600 network.inode-lru-limit: 50000 cluster.lookup-optimize: on server.event-threads: 4 client.event-threads: 4 [root@gqas013 ~]#
https://code.engineering.redhat.com/gerrit/#/c/102614/ Should fix the same
(In reply to Poornima G from comment #2) > https://code.engineering.redhat.com/gerrit/#/c/102614/ Should fix the same Wrong patch. I think this is same as https://bugzilla.redhat.com/show_bug.cgi?id=1411352, also looks unrelated to parallel readdir. We can retry once the fix for 1411352 is merged and if still reproducible we can take a look at it.
Given 1411352 is now moved to ON_QA, moving this bug to ON_QA
Fix for BZ1411352 seems to have fixed this problem as well ,cannot reproduce the reported issue anymore in 3.8.4-25.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774