Project

General

Profile

Actions

Bug #23380

closed

mds: ceph.dir.rctime follows dir ctime not inode ctime

Added by Dan van der Ster about 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Community (user)
Tags:
Backport:
luminous
Regression:
Yes
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The original intention of the rctime was reflect the latest inode ctime in the children: https://lkml.org/lkml/2008/7/15/385

As of v12.2.4 this does not seem to be the case .. it is following the latest dir ctime of the children:

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" 

I don't know when this regressed because I don't have any pre-luminous clusters left.


Related issues 2 (0 open2 closed)

Related to CephFS - Bug #35945: client: update ctime when modifying file contentResolvedZheng Yan09/11/2018

Actions
Copied to CephFS - Backport #23750: luminous: mds: ceph.dir.rctime follows dir ctime not inode ctimeResolvedPrashant DActions
Actions

Also available in: Atom PDF