relatime · shipping · also relatime, Relative atime, MS_RELATIME

Relative access-time updates

Relatime is a Linux policy that selects access-time updates using the existing access, modification and inode-change times and a daily age condition.

Related Observatory article: Relative access-time updates on hesela.com

In Linux v6.12, an otherwise eligible access passes the relatime test when mtime or ctime is at least as recent as atime, or when the difference between the current time and the stored atime, using their integer-second fields, reaches 86,400. Equality qualifies. This is checked during access, not by a daily timer updating idle files. Other update suppression and failure conditions still apply. [1]

Relatime selects updates; lazytime controls their persistence. noatime suppresses access-triggered updates, while strictatime requests traditional access-time behavior. These policies do not make atime a complete access log or a file-content identity. [2]

Relations

related
File access time, File modification time, Inode change time, Lazy timestamp persistence

Advantages

  • Can reduce access-driven timestamp updates compared with strict access-time policy.

Limitations

  • An unchanged atime does not establish that no read occurred.
  • The age condition is not a timestamp-persistence deadline.

Citations

  1. Linux v6.12 fs/inode.c: relatime_need_update and generic_update_time (accessed 2026-11-09)
  2. Linux mount(2): MS_LAZYTIME and timestamp policy (accessed 2026-11-09)

Further reading

  1. Hesela: timestamp selection is separate from persistence (accessed 2026-11-09)
Sources & caveats
  • Source synthesis of Linux API documentation and the pinned v6.12 implementation; no access-policy or power-loss experiment performed.

JSON: /data/terms/relatime.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Relative access-time updates. Hesela. 2026-11-09. https://hesela.dev/terms/relatime/