Sandip, What type of client are you using ? kernel client or fuse client ? If it's the kernel client, then it's a bug. FYI - Pacific and Quincy fuse clients do the right thing On Wed, May 24, 2023 at 9:24 PM Sandip Divekar < sandip.divekar@xxxxxxxxxxxxxxxxxx> wrote: > Hi Team, > > I'm writing to bring to your attention an issue we have encountered with > the "mtime" (modification time) behavior for directories in the Ceph > filesystem. > > Upon observation, we have noticed that when the mtime of a directory > (let's say: dir1) is explicitly changed in CephFS, subsequent additions of > files or directories within > 'dir1' fail to update the directory's mtime as expected. > > This behavior appears to be specific to CephFS - we have reproduced this > issue on both Quincy and Pacific. Similar steps work as expected in the > ext4 filesystem amongst others. > > Reproduction steps: > 1. Create a directory - mkdir dir1 > 2. Modify mtime using the touch command - touch dir1 > 3. Create a file or directory inside of 'dir1' - mkdir dir1/dir2 > Expected result: > mtime for dir1 should change to the time the file or directory was created > in step 3 > Actual result: > there was no change to the mtime for 'dir1' > > Note : For more detail, kindly find the attached logs. > > Our queries are : > 1. Is this expected behavior for CephFS? > 2. If so, can you explain why the directory behavior is inconsistent > depending on whether the mtime for the directory has previously been > manually updated. > > > Best Regards, > Sandip Divekar > Component QA Lead SDET. > > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > -- Milind _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |