On Wed, Mar 14, 2018 at 9:22 AM, Dan van der Ster <dan@xxxxxxxxxxxxxx> wrote: > Hi all, > > On our luminous v12.2.4 ceph-fuse clients / mds the rctime is not > tracking the latest inode ctime, but only the latest directory ctimes. > > Initial empty dir: > > # getfattr -d -m ceph . | egrep 'bytes|ctime' > ceph.dir.rbytes="0" > ceph.dir.rctime="1521043742.09466372697" > > Create a file, rctime is updated: > > # touch a > # getfattr -d -m ceph . | egrep 'bytes|ctime' > ceph.dir.rbytes="0" > ceph.dir.rctime="1521043831.0921836283" > > Modify a file, rbytes is updated but not rctime: > > # echo hello > a > # getfattr -d -m ceph . | egrep 'bytes|ctime' > ceph.dir.rbytes="6" > ceph.dir.rctime="1521043831.0921836283" > > Modify the dir, rctime is updated: > > # touch b > # getfattr -d -m ceph . | egrep 'bytes|ctime' > ceph.dir.rbytes="6" > ceph.dir.rctime="1521043861.09597651370" > > Do others see the same rctime behaviour? Is this how it's supposed to work? It appears rctime is meant to reflect changes to directory inodes. Traditionally, modifying a file (truncate, write) does not involve metadata changes to a directory inode. Whether that is the intended behavior is a good question. Perhaps it should be changed? -- Patrick Donnelly _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |