Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • Did anything on the client change after it was restarted? Do the logs say anything? Can nfsserver resolve clientserver? Have you tried to add /datalake/raw/org <ip_address>(ro,root_squash,sync) to /etc/fstab just to rule it out? Commented Jan 4, 2021 at 11:55
  • @NasirRiley Yeah, tried that. Added a line like nfsserver.org.local:/datalake/raw/org /datalake/org/raw/ nfs ro 0 0 to the clientserver's /etc/fstab and restarting, but not mounted and seeing same problem. What did you mean by "do the logs say anything"? What location could I check for any relevant logs here? Commented Jan 5, 2021 at 1:49
  • 1
    My mistake. That line should be added to /etc/exports and after, restart the nfs service. The line that you added to /etc/fstab is the name, not the IP address. Can you ping nfsserver from clientserver? The log that you can look at is /var/log/messages on the client and on the server. If you're going to use Linux, it's important to know to examine logs. Commented Jan 5, 2021 at 2:15
  • After running the mount command, I do see messages of the form "Jan 4 18:37:12 clientserver gssproxy: gssproxy[2557]: (OID: { 1 2 840 113554 1 2 2 }) Unspecified GSS failure. Minor code may provide more information, Client 'host/[email protected]' not found in Kerberos database", but not totally sure what this means (updated post with more info in any case) Commented Jan 5, 2021 at 21:16
  • 2
    Which security flavour is the mount supposed to use? Plain old sec=sys (1:1 mapping of users/groups, no user authentication), or Kerberos (sec=krb5/krb5i/krb5p)? The GSS error means that Kerberos is likely not configured properly. By the way, look into the kernel log dmesg to see any errors related to the mount. The mount utility itself will never give you a lot of details about what went wrong, because all it gets from the kernel is a single error code. Commented Jan 8, 2021 at 8:42