[Bug 1978426] Re: "ignore" mount option set for autofs is not observed

[Maarten Jacobs]

I'm attaching a document that details the steps to recreate the behavior
in LXC containers, as well as my observations for each of the versions
(Bionic, Focal, Jammy). I'll collect a few screenshots of Nautilus that
shows what it looks like for each of the versions and add that later.

Even without the screenshots this should be ample information for
somebody to investigate in more detail.

There are differences in how gio (and as a result perhaps other
applications) interpret the "autofs" filesystem type that is created for
autofs mounts. Whereas on Bionic gio doesn't report the autofs mount, it
is reported by gio on Focal and Jammy. Thus, when the filesystem is
actually mounted, you end up with two mounts reported by gio (albeit
each of a slightly different type).

Doesn't look like autofs is doing anything different but what gio
reports is definitely different.

** Attachment added: "Launchpad Bug 1978426 Description.odt"
   https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1978426/+attachment/5613662/+files/Launchpad%20Bug%201978426%20Description.odt

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1978426

Title:
  "ignore" mount option set for autofs is not observed

Status in autofs package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Expired

Bug description:
  I am thinking autofs is not the right package for this, but the
  behavior is related to it.

  I have various NFS mounts configured with autofs, and invariably all
  of these mounts are reported twice by 'mount' as well as 'gio mount
  -l'. Similarly my file manager (Thunar) also shows these mounts twice.

  When I run 'mount', I see the same mount twice:

  /etc/auto.<redacted> on /home/<redacted>/Documents type autofs (rw,relatime,fd=7,pgrp=11462,timeout=300,minproto=5,maxproto=5,direct,ignore,pipe_ino=167388)
  <redacted>:/storage/Documents on /home/<redacted>/Documents type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=<redacted>,local_lock=none,addr=<redacted>)

  I've anonymized the entries a bit. The first entry is created when the
  master map is read, the second one is the "actual" NFS mount (created
  when I access the mount point).

  I've enabled "use_ignore_mount_option" in my autofs.conf - not quite
  sure if that's what caused the "ignore" option to be included on the
  autofs entry. But "ignore" is on the autofs line, and by the
  description of that option, it should cause user space applications to
  ignore the mount. Which apparently isn't happening.

  Hence my earlier statement that I don't think autofs is the problem -
  I think it's doing what it's supposed to - but the other applications
  are not observing the mount option.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: autofs 5.1.6-2ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189
  Uname: Linux 5.4.0-117-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Jun 12 21:43:36 2022
  InstallationDate: Installed on 2013-05-04 (3326 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  SourcePackage: autofs
  UpgradeStatus: Upgraded to focal on 2022-03-18 (86 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1978426/+subscriptions