On 03/12/18 at 10:50, Adam Borowski wrote:
> On Mon, Dec 03, 2018 at 10:33:44AM +0100, Alessandro Selli wrote:
>> On 03/12/18 at 10:05, Adam Borowski wrote:
>>> realtime greatly reduces atime writes, but it's still too much.
>>   I wouldn't say so.  Since relatime updates atime only relative to the
>> present ctime and mtime, it's only changed when one of those two is
>> changed.  That is, updating atime does not require a separate write
>> operation.
> That was the original design -- but alas, it was later changed so the atime
> is updated at least once a day.


  My experience is inconsistent with what you write:

[alessandro@wkstn02 ~]$ mount | grep ' on /home '
/dev/mapper/part6_crypt_home on /home type ext4 (rw,relatime,nobarrier)
[alessandro@wkstn02 ~]$ stat .xsession-errors.old
  File: .xsession-errors.old
  Size: 47036242        Blocks: 91880      IO Block: 4096   regular file
Device: fd02h/64770d    Inode: 655383      Links: 1
Access: (0600/-rw-------)  Uid: ( 1000/ alessandro)   Gid: ( 1000/ alessandro)
Access: 2018-07-06 13:22:22.312846358 +0200
Modify: 2018-07-06 13:08:36.392798307 +0200
Change: 2018-07-06 13:22:17.149512721 +0200
 Birth: -
[alessandro@wkstn02 ~]$ date
Mon Dec  3 11:18:47 CET 2018
[alessandro@wkstn02 ~]$ uname -r
4.19.5.wkstn02-0
[alessandro@wkstn02 ~]$ 
 

[...]

> Every inode has to be updated.


  Only when it has to be updated.  That is, only when attributes or data
must be.



--
Alessandro Selli <alessandroselli@???>
VOIP SIP: dhatarattha@???
Chiave firma e cifratura PGP/GPG signing and encoding key:
BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE