From upstream tracker issue: """ Objects deep in directory tree are not visible without first performing 'ls' on all of its subpaths. As an example I have put one object into rgw bucket: s3cmd -c .s3cfg2 put test.txt s3://ganesha/a/b/c/d/f/g/h/i/j/k/l/test s3cmd -c .s3cfg2 ls s3://ganesha/ --recursive 2018-06-14 15:40 5 s3://ganesha/a/b/c/d/f/g/h/i/j/k/l/test The problem is that after mounting it with nfs the file is not immediately visible - I have to traverse all of the directories one by one. root@ganesha-test:/# mount -o vers=4.1 test-server:/ /mnt/tmp/ -v mount.nfs: timeout set for Thu Jun 14 17:41:18 2018 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.0.14,clientaddr=192.168.0.16' root@ganesha-test:/# ls /mnt/tmp/ ganesha test root@ganesha-test:/# ls /mnt/tmp/ganesha/ a root@ganesha-test:/# cat /mnt/tmp/ganesha/a/bhttps://github.com/nfs-ganesha/nfs-ganesha/issues/305/c/d/f/g/h/i/j/k/l/test cat: /mnt/tmp/ganesha/a/b/c/d/f/g/h/i/j/k/l/test: No such file or directory root@ganesha-test:/# ls /mnt/tmp/ganesha/ a root@ganesha-test:/# ls /mnt/tmp/ganesha/a/ b root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/ c root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/ d root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/d/ f root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/d/f/ g root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/d/f/g/ h root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/d/f/g/h/ i root@ganesha-test:/# cat /mnt/tmp/ganesha/a/b/c/d/f/g/h/i/j/k/l/test cat: /mnt/tmp/ganesha/a/b/c/d/f/g/h/i/j/k/l/test: No such file or directory root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/d/f/g/h/i/ j root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/d/f/g/h/i/j/ k root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/d/f/g/h/i/j/k/ l root@ganesha-test:/# ls /mnt/tmp/ganesha/a/b/c/d/f/g/h/i/j/k/l/ test root@ganesha-test:/# cat /mnt/tmp/ganesha/a/b/c/d/f/g/h/i/j/k/l/test test root@ganesha-test:/# """
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-2019:0475