Why doesn gfs_tool setflag inherit_directio affect new_files_directio?
If I do: [root@node-01#] gfs_tool setflag inherit_directio my_directory [root@node-01#] gfs_tool gettune my_directory It displays: new_files_directio = 0 Here’s what’s going on: inherit_directio and new_files_directio are two separate things. If you look at the man page, inherit_directio operates on a single directory whereas new_files_directio is a filesystem-wide “settune” value. If you do: gfs_tool setflag inherit_directio my_directory You’re telling the fs that ONLY your directory and all new files within that directory should have this attribute, which is why your tests are acting as expected, as long as you’re within that directory. It basically sets an attribute on an in-memory inode for the directory. If instead you were to do: gfs_tool settune mount-point new_files_directio 1 The value new_files_directio value would change for the whole mount point, not just that directory. Of course, you’re seeing what gfs_tool gettune my_directory is reporting for the global flag.
Related Questions
- What if I have limited dental benefits available through my Federal Employee Health Benefit (FEHB) Plan? How does this affect my MetLife dental claims?
- How will the Microsoft Kerberos implementation affect my access to non-Microsoft Kerberos services?
- Why doesn gfs_tool setflag inherit_directio affect new_files_directio?
