Date: Sun, 18 Jul 2021 20:01:20 +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-7Nov7SVrAB@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 #10 from Robert Wing <rew@FreeBSD.org> --- When using a direct map with a wildcard entry and doing "cd /net/nonexisten= t", a new directory will be created. W.R.T. a special_users map, just because t= he user exists on the system doesn't necessarily mean that the users home directory is being exported via NFS, no? The temporary mountpoint should definitely be cleaned up on failure. I supp= ose this cleanup should happen after autofs has exhausted its retry attempts? Do you think autofs or automountd (via request from autofs) should do the clean up? Quick glance through the code; looks like it would be a bit of work to make= the mount_nfs bits public that would allow automountd to retrieve the error code that was returned from the NFS server.. There's not a reliable way to discover exported directories for NFSv3/NFSv4? I think in a perfect world, the program flow would be: 1. request to automountd to mount from a NFS server 2. automountd checks if that directory is exported from the NFS server 3. if yes, create the temporary mountpoint 4. attempt the mount 5. if error, remove temporary mountpoint and return the error code to autofs 6. let autofs, based on the error code, decide if it wants to retry to moun= t. But, it's not a perfect world, is it? --=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-7Nov7SVrAB>