Set autofs to nfs4 #158
Merged
Set autofs to nfs4 #158
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove comments from this file, as they would not be updated when autofs is updated. Refer to the man page instead.
From autofs.conf(5): mount_nfs_default_protocol Specify the default protocol used by mount.nfs(8) (program default 3). Since we can't identify this default automatically we need to set it in the autofs configuration. Our mount.fs defaults to nfs4, so configure this correctly. Background: autmount tries to avoid to call mount.nfs for a host, when the host or the nfs service on the host is not available to avoid long timeouts (and possibly use a alternative ip-address or server). So it uses rpc calls to the null procedure of the relevant nfs version. If a map entries specifies a version option for nfs, then it is clear, what this relevant version is. But if no version is specified in the map entry, automounts wants to poll the version(s) mount.nfs would use, if no version is specified. Per default, it is assumed, that mount.nfs tries nfs3 and 2, so this is what gets polled. As we only offer nfs4, we get the error `mount(nfs): no hosts available`. We need to tell automount, that our mount.nfs defaults to nfs4 so that nfs4 is polled. The above error doesn't occur with our current version of nfs-utils (which is 2.4.1). In this version, `mount.nfs` is so old, that it doesn't show its version number when called as `mount.nfs -V`. In that case, autofs skips the probing of nfs-versions alltogether. However, when nfs-utils is upgraded to 2.5.4, autofs will detect that and we get the error. So the change here is a prerequisite for an update of nfs-utils. This new setting is valid for autofs version 5.1.3 and for autofs version 5.1.7, so there is no issue with the concurrently ongoing update of autofs.
donald
force-pushed
the
set-autofs-to-nfs4
branch
from
f6fa3ce
to
ff6c668
Compare
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tell automount that our mount.nfs defaults to nfs4 if no version is specified.
This fixes the client-side problem of mariux64/bee-files#2043