Nfs3 Network Error
Contents |
memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. IESG Note Internet Engineering Steering Group comment: please note that the IETF is not involved in creating or maintaining this specification. This is the significance of the specification not being on the standards track. Abstract This paper describes the NFS version 3 protocol. This paper is provided so that people can write compatible implementations. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . kernel: nfs: server not responding, still trying . . . . . . 3 1.1 Scope of the NFS version 3 protocol . . . . . . . . . . 4 nfs server not responding still trying solaris 1.2 Useful terms . . . . . . . . . . . . . . . . . . . . . . 5 1.3 Remote Procedure Call . . . . . . . . . .
Mount.nfs: Connection Timed Out
. . . . . . . 5 1.4 External Data Representation . . . . . . . . . . . . . . 5 1.5 Authentication and Permission Checking . . . . . . . . . 7 1.6 Philosophy . . . . . . . . . . . . . . . . . . . . .
Mount Nfs Version 3
. . 8 1.7 Changes from the NFS version 2 protocol . . . . . . . . 11 2. RPC Information . . . . . . . . . . . . . . . . . . . . . 14 2.1 Authentication . . . . . . . . . . . . . . . . . . . . . 14 2.2 Constants . . . . . . . . . . . . . . . . . . . . . . . 14 2.3 Transport address . . . . . . . . . . . . . . . . . . . 14 2.4 Sizes . . . . . . . . . . . . clnt_create: rpc: program not registered . . . . . . . . . . . . . 14 2.5 Basic Data Types . . . . . . . . . . . . . . . . . . . . 15 2.6 Defined Error Numbers . . . . . . . . . . . . . . . . . 17 3. Server Procedures . . . . . . . . . . . . . . . . . . . . 27 3.1 General comments on attributes . . . . . . . . . . . . . 29 3.2 General comments on filenames . . . . . . . . . . . . . 30 3.3.0 NULL: Do nothing . . . . . . . . . . . . . . . . . . . . 31 Callaghan, el al Informational [Page 1] RFC 1813 NFS Version 3 Protocol June 1995 3.3.1 GETATTR: Get file attributes . . . . . . . . . . . . . . 32 3.3.2 SETATTR: Set file attributes . . . . . . . . . . . . . . 33 3.3.3 LOOKUP: Lookup filename . . . . . . . . . . . . . . . . 37 3.3.4 ACCESS: Check access permission . . . . . . . . . . . . 40 3.3.5 READLINK: Read from symbolic link . . . . . . . . . . . 44 3.3.6 READ: Read from file . . . . . . . . . . . . . . . . . . 46 3.3.7 WRITE: Write to file . . . . . . . . . . . . . . . . . . 49 3.3.8 CREATE: Create a file . . . . . . . . . . . . . . . . . 54 3.3.9 MKDIR: Create a directory . . . . . . . . . . . . . . . 58 3.3.10 SYMLINK: Create a symbolic link . . . . . . . . . . . . 61 3.3.11 MKNOD: Create a special device . . . . . . . . . . . . . 63 3.3.12 REMOVE: Remove a
Reference HOWTO FAQs RFCs nfsv4 mounts files and directories as nobody rpcbind failure error server not responding error NFS client fails a reboot error service not responding error program not registered error stale file handle error unknown host error mount point error no such file
Nfsstat
error No such file or directory The first thing is to determine with one version of nfs mount options protocol you encounter the problem. Is this NFS3 and NFS4? For example RHEL 6 by default uses NFS4 for mounting other RHEL 6 systems. mount.nfs: requested nfs version or transport protocol is not supported So you can get NFS4 mount even if you do not suspect specifying NFS4 explicitly. This is due to the fact that nfs4 keyword in /etc/fstab is deprecated and now client starts asking for services starting with NFS4 not NFS3 https://tools.ietf.org/html/rfc1813 like before. NFS 3 is conceptually elegant and rather simple, and difficult to troubleshoot problems are more often due to the complexity of the environment then protocol itself. It's comely opposite with NFS4. NFS 4 is much more complex and less reliable. It was mostly created by NetApps guys who wanted to compete with SAN based appliances and they overcooked the protocol trying to improve the transmission speed. For example, NFS4 often demonstrate spontaneous problem with mount points, when http://www.softpanorama.org/Net/Application_layer/NFS/troubleshooting_of_nfs_problems.shtml umount operation just hangs and/or mounted directory became inaccessible. It is very difficult to escape from this situation in RHEL 6 and derivatives without rebooting the server. In such cases the best way to avoid headache is to downgrade version of NFS to 3. We will limit ourselves discussion of NFS3 protocol as downgrading of NFS4 to NFS3 is kind of universal troubleshooting method for NFS4: if problem persists then you can problem=lsioot it in NFS 3 and the switch back. If problem disappears that it is doe to flaky implementation of NFS3. So everywhere below NFS means NFS3. For example NFS 4 is more picky and can mount directories with nobody:nobody permissions when NFS3 mounts it correctly. See nfsv4 mounts files and directories as nobody Most problem with NFS3 are not connected with protocol per se, but more like environment, infrastructure within which it operates. Among "infrastructure induced" NFS problems are: Different DNS name (or IP addressed) on NFS server then that actual client DNS name. Start debugging by verifying that DNS names (or IP addresses if they are used for exporting filesystem), are the same on the NFS server and client. Different uid's for the same usernames or groups NFS hostile firewall Problems with DNS which causes timeouts Among common NFS3 errors we can specifically list the following: nfsv4 mounts files and directories as nobody The rpcbind failure error The server not responding error
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://serverfault.com/questions/374597/mounting-nfs3-using-kerberos-and-ad more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges http://nfs.sourceforge.net/nfs-howto/ar01s07.html Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Mounting NFS3 using Kerberos and AD up vote 8 down vote favorite 1 server not I've got a Linux server (Centos 5.6) that needs to automount home directories from a Windows (Server 2008) NFS share using Kerberos. The share mounts (with the nobody user and group) if authentication is turned off. However, if the -o sec=krb5 flag is passed, I get mount.nfs: permission denied. As root, I used kinit to get a ticket, and klist tells me that it's a valid ticket. Googling the error didn't give much, as it seems to server not responding be a bit of a catch-all. Nothing useful was found in any of the logs I looked in. Root access is set to allowed on the Windows share. Because of the sharing from Windows thing, a lot of the resources saying to change server settings don't apply as directly. Any ideas for getting this to work? linux windows-server-2008 nfs share|improve this question asked Mar 28 '12 at 20:15 Ethan 11118 1 Are you sure that windows can export in NFS4? AFAIK you need NFS4 to use kerberos. –wazoox Apr 6 '12 at 21:00 Sorry, it's NFS3. Windows - to my knowledge - only supports NFS3. However, the options page for NFS in Windows lists KRB5 and KRB5i as options, so I assumed that it worked. –Ethan Apr 7 '12 at 22:08 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote OK, after a bit of research I've found this article that explains how to achieve what you're looking for with a Solaris client. By looking at the client part of this other documentation maybe you could get the whole stuff working... Apparently from what I've seen from looking around making NFS3 under linux authenticate against kerberos should be possible, contrary to what I thought; however information is incredibly scarce. In the worst case what's preventing you from using CIFS mount? Af
See Files on a Mounted File System First, check to see if the file system is actually mounted. There are several ways of doing this. The most reliable way is to look at the file /proc/mounts, which will list all mounted filesystems and give details about them. If this doesn't work (for example if you don't have the /proc filesystem compiled into your kernel), you can type mount -f although you get less information. If the file system appears to be mounted, then you may have mounted another file system on top of it (in which case you should unmount and remount both volumes), or you may have exported the file system on the server before you mounted it there, in which case NFS is exporting the underlying mount point (if so then you need to restart NFS on the server). If the file system is not mounted, then attempt to mount it. If this does not work, see Symptom 3. 7.2. File requests hang or timeout waiting for access to the file This usually means that the client is unable to communicate with the server. See Symptom 3 letter b. 7.3. Unable to mount a file system There are two common errors that mount produces when it is unable to mount a volume. These are: failed, reason given by server: Permission denied This means that the server does not recognize that you have access to the volume. Check your /etc/exports file and make sure that the volume is exported and that your client has the right kind of access to it. For example, if a client only has read access then you have to mount the volume with the ro option rather than the rw option.Make sure that you have told NFS to register any changes you made to /etc/exports since starting nfsd by running the exportfs command. Be sure to type exportfs -ra to be extra certain that the exports are being re-read.Check the file /proc/fs/nfs/exports and make sure the volume and client are listed correctly. (You can also look at the file /var/lib/nfs/xtab for an unabridged list of how all the active export options are set.) If they are not, then you have not