By default the expire of automounted mounts depends on the
last access. In very large environments this helps reduce the number of mount requests from clients which can be significant.
But this can lead to mounts not being umounted when monitoring services scan directory trees containing automounts. In this case it can be beneficial to expire mounts based on whether they are actually in use (ie. contain a process working directory of open files), the so-called strict expire.
To allow for this later case a master map entry mount option, strictexpire, has been added. This mount option causes mounts to expire based on whether they are actually in use.
To enable this behaviour the mount option "strictexpire" needs to be added to automount master map entries and the expire behaviour will change if the kernel in use supports it.
NOTE when RHEL8.1 ships we will need to update this Kbase solution similar to what was done for RHEL7.7:
https://access.redhat.com/solutions/3225981
I tried adding it to the bug but apparently the latest bugzilla updates seem to have broken that because I always get an error now when trying to add it.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:3639
Created attachment 1559722 [details] Patch - add strictexpire mount option