On Fri, 2020-10-02 at 10:27 +0800, Ian Kent wrote: > On Thu, 2020-10-01 at 16:22 -0500, Eric Sandeen wrote: snip ... > > > > Backing up a bit, which xfsprogs utility saw this behavior with > > autofs mounts? > > IIRC the problem I saw ended up being with xfs_spaceman invoked > via udisksd on mount/umount activity. There may be other cases so > I'd rather not assume there won't be problems elsewhere but those > checks for an xfs fs that I didn't notice probably need to change. Looking around further, there may be another assumption that's not right. It looks like xfs_info is being called via udisksd -> libblockdev and the xfd_open() triggers the mount not a statfs() call as thought. I can't see why I saw xfs_spaceman hanging around longer than I thought it should so I probably don't have the full story. It's a bit academic though because there are good reasons to ignore autofs mounts in the libfrog functions, platform_check_mount() and fs_table_initialise_mounts(). If an autofs user has large direct mount maps there can be thousands of distinct mount table entries which, mostly, if not always, serve no useful purpose to utilities. They just add overhead so getting rid of them at the earliest opportunity is the sensible thing to do. In fact, before the mtab was symlinked to the proc mount table, I simply didn't update the mount table for autofs fs mounts so they never appeared and there were never any problem reports due to doing this. I could go on (and on) about this, but I'm starting to digress ... Ian
