Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Jul 2021 20:27:43 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 243551] Cannot checkout src tree in automounted $HOME
Message-ID:  <bug-243551-227-D53TO4Z34w@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-243551-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-243551-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243551

--- Comment #7 from Robert Wing <rew@FreeBSD.org> ---
(In reply to Edward Tomasz Napierala from comment #6)

Sure would be nice to have the errno from the failing mount program=20=20=
=20=20=20=20=20=20=20=20=20=20=20
as it exited.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20

I *think* this is what's happening:=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20

1. automountd creates /home/foobar because it needs somewhere to mount the
   NFS filesystem.
2. automountd attempts to mount_nfs /home/foobar from the nfs server.=20=20=
=20
3. The nfs server replies with ENOENT (because /home/foobar doesn't exist on
   server).
4. the mount program fails and exits with status code 1.=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
5. automountd doesn't remove /home/foobar after the failed mount.=20=20=20=
=20=20=20=20

One thought is; make a special case for NFS that checks if the target=20=20=
=20=20=20=20=20=20=20=20=20
directory is exported from the NFS server before attempting to mount it.=20=
=20=20=20=20=20=20=20
Not sure how feasible this idea is, I'd have to look into it..or maybe one=
=20=20
of you know off the top of your head?=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20

I imagine an issue with doing a special case for NFS is that other automoun=
ted
filesystems may have similar problems as well (but in a different way). Sti=
ll,
given that NFS seems to be the largest use-case for automount, it may be wo=
rth
making a special case for NFS, even if the problem remains for other
automounted filesystems. This is why I mentioned it would be nice to have t=
he
errno from the failing mount program as it *might* work as general solution=
 for
other automounted filesystems.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243551-227-D53TO4Z34w>