The fix is merged in Ceph main branch. I've created a quincy backport PR https://github.com/ceph/ceph/pull/48520 for the respective quincy backport tracker https://tracker.ceph.com/issues/57879
Hemanth, I'm copying over the steps from https://tracker.ceph.com/issues/57210 I used to reproduce this issue in a Ceph cluster without needing OpenStack manila . I used a vstart cluster, but the steps should be the same in a QE test cluster ``` $ ./bin/ceph fs volume create a $ ./bin/ceph fs subvolume create a subvol01 $ ./bin/ceph fs subvolume getpath a subvol01 $ ./bin/ceph nfs cluster create nfs-ganesha $ ./bin/ceph nfs export create cephfs nfs-ganesha /cephfs3 a `./bin/ceph fs subvolume getpath a subvol01` $ sudo mount.nfs4 127.0.0.1:/cephfs3 /mnt/nfs1/ $ pushd /mnt/nfs1/ $ sudo touch file00 $ # can see newly created file when listing directory contents $ ls file00 $ popd $ ./bin/ceph fs subvolume snapshot create a subvol01 snap01 $ ./bin/ceph fs subvolume snapshot clone a subvol01 snap01 clone01 $ ./bin/ceph nfs export create cephfs nfs-ganesha /cephfs4 a `./bin/ceph fs subvolume getpath a clone01` $ sudo mount.nfs4 127.0.0.1:/cephfs4 /mnt/nfs2/ $ pushd /mnt/nfs2/ $ ls file00 $ sudo touch file01 $ # can see cloned 'file00' but cannot see the newly created file 'file01' when reading the directory contents within the clone $ ls file00 ``` With this fix, you should be able to see the newly created 'file01' too in the FS subvolume clone when listing using the NFS client.
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 (Red Hat Ceph Storage 6.0 Bug Fix update), 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-2023:1360