Few things need atime at all, even fewer things need synchronous durability guarantees for atime (I'm not aware of any). So writing it out in the background (either when evicting disk cache or after 24h) while keeping the in-memory representation up to date is good enough for most use-cases.
That advice is mostly obsolete, lazytime has been a thing for years.
Well, same point: keeping track of atime is way too expensive and barely useful.
Lazytime is a pretty good hack, but it doesn't survive a crash, does it?
Few things need atime at all, even fewer things need synchronous durability guarantees for atime (I'm not aware of any). So writing it out in the background (either when evicting disk cache or after 24h) while keeping the in-memory representation up to date is good enough for most use-cases.
1 reply →
lazytime isn't default though is it? So changing fs time options is still useful advice.
Did this for a mdadm raid system using btrfs and the difference was very noticeable on a CI build machine.