With the additional information in https://bugs.launchpad.net/snapd/+bug/1821193 I think we can fix this issue quickly.
1) The mountinfo parser will now look for an automount point that mentions autofs, an example line is mentioned here:
137 29 0:50 / /home rw,relatime shared:87 - autofs /etc/auto.master.d/home rw,fd=7,pgrp=22588,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=173399
2) We could optionally look at the referenced file (/etc/auto.master.d/home) and parse it, in this case it contains this line (among others)
* -fstype=nfs,vers=4,rw,soft,rsize=8192,wsize=8192 prodpeda-samba.domain.fr:/home/&
With this information we can enable the workaround reliably.
I will not do 2) at first, unless reviewers deem it necessary.
With the additional information in https:/ /bugs.launchpad .net/snapd/ +bug/1821193 I think we can fix this issue quickly.
1) The mountinfo parser will now look for an automount point that mentions autofs, an example line is mentioned here:
137 29 0:50 / /home rw,relatime shared:87 - autofs /etc/auto. master. d/home rw,fd=7, pgrp=22588, timeout= 300,minproto= 5,maxproto= 5,indirect, pipe_ino= 173399
2) We could optionally look at the referenced file (/etc/auto. master. d/home) and parse it, in this case it contains this line (among others)
* -fstype= nfs,vers= 4,rw,soft, rsize=8192, wsize=8192 prodpeda- samba.domain. fr:/home/ &
With this information we can enable the workaround reliably.
I will not do 2) at first, unless reviewers deem it necessary.