[DragonFlyBSD - Bug #3324] Re: DragonFly automountd NFS mounting broken

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Fri Oct 7 01:46:05 PDT 2022


Issue #3324 has been updated by arcade at b1t.name.


Sorry, probably I wasn't quite clear in my email. I guess I said direct mounts are not working while showing they are... Doh.

Direct mounts have mount directory so they are just escaping this bug. For example with:

/etc/auto_master:
/- -noauto

/etc/fstab:
/dev/serno/13I0LM9AS.s0         /mnt/efi        msdos   rw,noauto        2       2

arcade at probe2\/etc/mrc# ls /mnt/efi
boot0  boot1.efi  efi  System Volume Information

arcade at probe2\/etc/mrc# mount | grep autofs
map -hosts on /net (autofs)
map -noauto on /mnt/efi (autofs, automounted, local)
map -noauto on /mnt/cd (autofs)

Here /mnt/efi is correctly automounted on request.

Indirect maps are a little bit different, as they just provide the first directory, but everything under it might be dynamically created:

> mount | grep net
map -hosts on /net (autofs)

> ls /net/limbo/
"/net/limbo/": Not a directory (os error 20)

What happens here is:

1. Systems requests contents of /net/.
2. automountd receives request and uses `-hosts` map to resolve whether that directory is present, in this case whether hostname is resolvable.
3. Upon receiving responce from `-hosts` map autmountd attempts to create virtual directory `/net/<hostname>/` to use as a mountpoint base.
4. automountd attempts to list contents of that directory according to map.

And here we are getting an error. Something is getting wrong inside virtual autofs mount, when virtual directory is getting created:

Oct  7 11:42:15 probe2 automountd[127811]: cannot create /net/limbo: Invalid argument

It looks like some basic filesystem calls have changed and automountd is now unable to properly work with it's virtual autofs filesystem.

Hope that clears up what happens on my side. Sorry for disinformation.

----------------------------------------
Bug #3324: Re: DragonFly automountd NFS mounting broken
http://bugs.dragonflybsd.org/issues/3324#change-14404

* Author: tkusumi
* Status: Closed
* Priority: Normal
* Target version: 6.4
* Start date: 2022-09-05
----------------------------------------
<pre>
Right now when I try using autofs to automount NFS shares it fails each
time with the same error. Can't tell when it was definitely working, but
that was more then a month ago:

<snip>

Probably this has something to do with automountd indirect directories,
that's why direct mounts are not working.
</pre>

I don't have any issue with automount with indirect map.

Also note that these intermediate directories in indirect map have nothing to do with autofs itself.
These are just regular directories in parent directory's filesystem.

<pre><code class="shell">
# cat /etc/auto_master
# $FreeBSD$
#
# Automounter master map, see auto_master(5) for details.
#
#/net           -hosts          -nobrowse,nosuid,intr
# When using the -media special map, make sure to edit devd.conf(5)
# to move the call to "automount -c" out of the comments section.
#/media         -media          -nosuid,noatime
#/-             -noauto
/mnt/a/b/c/d/e          auto_nfs
# cat /etc/auto_nfs
NFS -intr,nfsv3 192.168.0.123:/mnt/exports
# automount -L
/mnt/a/b/c/d/e                                  auto_nfs             # indirect map referenced at /etc/auto_master:10
# mount | grep autofs
map auto_nfs on /mnt/a/b/c/d/e (autofs)
# mount | grep automounted
# tree /mnt/a > /dev/null    <------ this is where a/b/c/d/e are mkdir'ed before automount
# mount | grep automounted
192.168.0.123:/mnt/exports on /mnt/a/b/c/d/e/NFS (nfs, automounted)
</code></pre>




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


More information about the Bugs mailing list