[LU-17309] set timestamp on llog objects at creation time

• Status: Open
• Project: Lustre
• Affects Version/s: Lustre 2.15.0
• Type: Improvement
• Priority: Minor
• Reporter: Andreas Dilger
• Assignee: WC Triage
• Resolution: Unresolved
• Labels: easy
• Severity: 3

Description

For debugging purposes, it would be useful to store the ctime for an llog object when it is created. Otherwise, the objects currently do not set any timestamp on the log even though it was recently created (e.g. the 39xx logs, the low-numbered 2015 objects were created with an older Lustre version):

     9851      4 -rw-r--r--   1  root     root            8 Nov  7  2013 /mnt/tmp/O/1/LAST_ID
     1850     20 -rw-r--r--   1  root     root        19584 May  6  2015 /mnt/tmp/O/1/d4/164
    98363     12 -rw-r--r--   1  root     root         8448 Dec 31  1969 /mnt/tmp/O/1/d4/3972
     1665     20 -rw-r--r--   1  root     root        17792 May  6  2015 /mnt/tmp/O/1/d0/160
     1849     12 -rw-r--r--   1  root     root         8256 Apr 23  2015 /mnt/tmp/O/1/d30/158
     1861     20 -rw-r--r--   1  root     root        17472 May  6  2015 /mnt/tmp/O/1/d6/166
    98365     12 -rw-r--r--   1  root     root         8448 Dec 31  1969 /mnt/tmp/O/1/d6/3974
  2130157     12 -rw-r--r--   1  root     root         8384 Dec 31  1969 /mnt/tmp/O/1/d8/3976

Similarly, it would also be useful to update the mtime when a catalog is modified, since this doesn't happen very often and otherwise they show the timestamp when the file was created (maybe not even that for newer versions of Lustre):

    4 -rw-r--r--.  1 root        160 May  6  2015 CATALOGS
  180 -rw-r--r--.  1 root     176576 Nov  7  2013 changelog_catalog
   12 -rw-r--r--.  1 root       8384 Nov  7  2013 changelog_users