Le 15/12/2015 02:49, Duncan a écrit : > Christoph Anton Mitterer posted on Tue, 15 Dec 2015 00:25:05 +0100 as > excerpted: > >> On Mon, 2015-12-14 at 22:30 +0100, Lionel Bouton wrote: >> >>> I use noatime and nodiratime >> FYI: noatime implies nodiratime :-) > Was going to post that myself. Is there some reason you: > > a) use nodiratime when noatime is already enabled, despite the fact that > the latter already includes the former, or
I don't (for some time). I didn't check for nodiratime on all the systems I admin so there could be some left around but as they are harmless I only remove them when I happen to stumble on them. > > b) didn't sufficiently research the option (at least the current mount > manpage documents that noatime includes nodiratime under both the noatime > and nodiratime options, I just checked: this has only be made crystal-clear in the latest man-pages version 4.03 released 10 days ago. The mount(8) page of Gentoo's current stable man-pages (4.02 release in August) which is installed on my systems states for noatime: "Do not update inode access times on this filesystem (e.g., for faster access on the news spool to speed up news servers)." This is prone to misinterpretation: directories are inodes but that may not be self-explanatory for everyone. At least it could leave me with a doubt if I wasn't absolutely certain of the behavior (see below): I'm not sure myself that there isn't a difference between a VFS inode (the in-memory structure) and an on-disk structure called inode which some filesystems may not have (I may have been mistaken but IIRC ReiserFS left me with the impression that it wasn't storing directory entries in inodes or it didn't call it that). In fact I remember that when I read statements about noatime implying nodiratime I had to check fs/inode.c after I found a random discussion on the subject mentioning the proof being in the code to make sure of the behavior. > and at least some hint of that has been in the > manpage for years as I recall reading it when I first read of nodiratime > and checked whether my noatime options included it) before standardizing > on it, or > > c) might have actually been talking in general, and there's some mounts > you don't actually choose to make noatime, but still want nodiratime, or I probably used this case for testing purposes (but don't remember a case where it was useful to me). The expression I used was not meant to describe the exact flags in fstab on my systems but the general idea of avoiding files and directories atime updates as by using noatime I'm implicitly using nodiratime too. Sorry for the confusion (I've been confused about the subject a long time which probably didn't help express myself clearly). Best regards, Lionel -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
