On Tue, Aug 21, 2018 at 10:10:04AM -0400, Austin S. Hemmelgarn wrote: > On 2018-08-21 09:32, Janos Toth F. wrote: > >>>> so pretty much everyone who wants to avoid the overhead from them can > >>>> just > >>>> use the `noatime` mount option. > > > > It would be great if someone finally fixed this old bug then: > > https://bugzilla.kernel.org/show_bug.cgi?id=61601 > > Until then, it seems practically impossible to use both noatime (this > > can't be added as rootflag in the command line and won't apply if the > > kernel already mounted the root as RW) and space-cache-v2 (has to be > > added as a rootflag along with RW to take effect) for the root > > filesystem (at least without an init*fs, which I never use, so can't > > tell). > > > Last I knew, it was fixed. Of course, it's been quite a while since I > last tried this, as I run locally patched kernels that have `noatime` as > the default instead of `relatime`.
I'm using VMs without initrd, tested the rootflags=noatime and it still fails, the same way as in the bugreport. As the 'noatime' mount option is part of the mount(2) API (passed as a bit via mountflags), the remaining option in the filesystem is to whitelist the generic options and ignore them. But this brings some layering violation question. On the other hand, this would be come confusing as the user expectation is to see the effects of 'noatime'.
