Also having NFSv4 problems
Amadeus W.M.
amadeus84 at verizon.net
Mon Jan 4 00:42:01 UTC 2010
On Sun, 03 Jan 2010 18:02:03 -0600, Robert G. (Doc) Savage wrote:
> I have mirrors of several repositories a 1TB hardware raid array mounted
> as /pub on a RHEL54 server. I want to locally export that to several F12
> laptops and desktop machines on a gigabit home network using nfs4. I'm
> having trouble getting F12 nfs4 clients to mount the exported directory
> on the RHEL54 server. The error I'm getting on the F12 client is:
>
>
> # mount -v -t nfs4 -o rsize=8192,wsize=8192,timeo=14,intr
> lion:/pub /lion mount.nfs4: timeout set for Sun Jan 3 17:16:25
> 2010 mount.nfs4: trying text-based options
>
'rsize=8192,wsize=8192,timeo=14,intr,addr=192.168.1.2,clientaddr=192.168.1.7'
> mount.nfs4: mount(2): Operation not permitted mount.nfs4:
> Operation not permitted
>
>
> Local details:
> RHEL54 server 'lion' = 192.168.1.2
> /etc/exports = *(rw), owned by root, permissions 644 F12 laptop 'tiger'
> = 192.168.1.7
>
> The server looks fine:
>
>
> # service nfs restart
> Shutting down NFS mountd: [ OK
> ] Shutting down NFS daemon: [
> OK ] Shutting down NFS quotas:
> [ OK ] Shutting down NFS services:
> [ OK ] Starting NFS services:
> [ OK ] Starting NFS quotas:
> [ OK ] Starting NFS daemon:
> [ OK ] Starting NFS mountd:
> [ OK ]
>
>
> The problem appears to be on the F12 client side:
>
> # service nfs restart
> Shutting down NFS mountd:
> [FAILED] Shutting down NFS daemon:
> [ OK ] Shutting down NFS quotas:
> [ OK ] Shutting down NFS services:
> [FAILED] Starting NFS services:
> [ OK ] Starting NFS quotas:
> [ OK ] Starting NFS daemon:
> [ OK ] Starting NFS mountd: Usage:
> rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d
> kind|--debug kind]
> [-o num|--descriptors num] [-f
> exports-file|--exports-file=file] [-p|--port port] [-V
> version|--nfs-version version] [-N
> version|--no-nfs-version version] [-n|--no-tcp] [-H
> ha-callout-prog] [-s|--state-directory-path path]
> [-g|--manage-gids] [-t num|--num-threads=num]
>
[FAILED]
>
>
> About four years ago I was able to set up a similar arrangement using
> nfs3 on RHEL4 and F6, but this is my first attempt with nfs4. I seem to
> be having the same problem Robert P.J. Day is having with rpc.mountd.
>
> --Doc Savage
> Fairview Heights, IL.0
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML>
> <HEAD>
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
> <META NAME="GENERATOR" CONTENT="GtkHTML/3.16.3">
> </HEAD>
> <BODY>
> I have mirrors of several repositories a 1TB hardware raid array mounted
> as /pub on a RHEL54 server. I want to locally export that to several F12
> laptops and desktop machines on a gigabit home network using nfs4. I'm
> having trouble getting F12 nfs4 clients to mount the exported directory
> on the RHEL54 server. The error I'm getting on the F12 client is:<BR>
> <BR>
> <BLOCKQUOTE>
> <PRE>
> <FONT SIZE="1"># mount -v -t nfs4 -o rsize=8192,wsize=8192,timeo=14,intr
> lion:/pub /lion</FONT> <FONT SIZE="1">mount.nfs4: timeout set for Sun
> Jan 3 17:16:25 2010</FONT> <FONT SIZE="1">mount.nfs4: trying
> text-based options
>
'rsize=8192,wsize=8192,timeo=14,intr,addr=192.168.1.2,clientaddr=192.168.1.7'</
FONT>
> <FONT SIZE="1">mount.nfs4: mount(2): Operation not permitted</FONT>
> <FONT SIZE="1">mount.nfs4: Operation not permitted</FONT>
>
> </PRE>
> </BLOCKQUOTE>
> Local details:<BR>
> RHEL54 server 'lion' = 192.168.1.2<BR> /etc/exports = *(rw), owned by
> root, permissions 644<BR> F12 laptop 'tiger' = 192.168.1.7<BR>
> <BR>
> The server looks fine:<BR>
> <BR>
> <BLOCKQUOTE>
> <PRE>
> <FONT SIZE="1"># service nfs restart</FONT> <FONT SIZE="1">Shutting down
> NFS
>
mountd:
> [ OK ]</FONT> <FONT SIZE="1">Shutting down NFS
>
daemon:
> [ OK ]</FONT> <FONT SIZE="1">Shutting down NFS
>
quotas:
> [ OK ]</FONT> <FONT SIZE="1">Shutting down NFS
>
services:
> [ OK ]</FONT> <FONT SIZE="1">Starting NFS
>
services:
> [ OK ]</FONT> <FONT SIZE="1">Starting NFS
>
quotas:
> [ OK ]</FONT> <FONT SIZE="1">Starting NFS
>
daemon:
> [ OK ]</FONT> <FONT SIZE="1">Starting NFS
>
mountd:
> [ OK ]</FONT> </PRE>
> </BLOCKQUOTE>
> <BR>
> The problem appears to be on the F12 client side: <BLOCKQUOTE>
> <PRE>
> <FONT SIZE="1"># service nfs restart</FONT> <FONT SIZE="1">Shutting down
> NFS
>
mountd:
> [FAILED]</FONT> <FONT SIZE="1">Shutting down NFS
>
daemon:
> [ OK ]</FONT> <FONT SIZE="1">Shutting down NFS
>
quotas:
> [ OK ]</FONT> <FONT SIZE="1">Shutting down NFS
>
services:
> [FAILED]</FONT> <FONT SIZE="1">Starting NFS
>
services:
> [ OK ]</FONT> <FONT SIZE="1">Starting NFS
>
quotas:
> [ OK ]</FONT> <FONT SIZE="1">Starting NFS
>
daemon:
> [ OK ]</FONT> <FONT SIZE="1">Starting NFS mountd: Usage:
> rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug
> kind]</FONT> <FONT SIZE="1">
> [-o num|--descriptors num] [-f exports-file|--exports-file=file]</FONT>
> <FONT SIZE="1"> [-p|--port
> port] [-V version|--nfs-version version]</FONT> <FONT
> SIZE="1"> [-N
> version|--no-nfs-version version] [-n|--no-tcp]</FONT> <FONT
> SIZE="1"> [-H ha-callout-prog]
> [-s|--state-directory-path path]</FONT> <FONT
> SIZE="1"> [-g|--manage-gids]
> [-t num|--num-threads=num]</FONT> <FONT
>
SIZE="1">
> [FAILED]</FONT> </PRE>
> </BLOCKQUOTE>
> <BR>
> About four years ago I was able to set up a similar arrangement using
> nfs3 on RHEL4 and F6, but this is my first attempt with nfs4. I seem to
> be having the same problem Robert P.J. Day is having with
> rpc.mountd.<BR> <BR>
> --Doc Savage<BR>
> Fairview Heights, IL.0<BR>
> <BR>
> </BODY>
> </HTML>
You don't need nfs running on the client.
You didn't show what the server is exporting, to whom, permissions, etc.
Are you actually exporting /pub to 192.168.1.0/24 ?
If you have a firewall, you must open some ports on the server in order
for any client to connect to the server. Try without the firewall first.
What I do and works as expected is this:
On the server run system-config-nfs
Add the partitions you want to export to 192.168.1.0/24 with whatever
permissions you want. Then click on the "Server Settings" and force the
nfs daemons to run on designated ports of your choice. E.g. 4000 - 4003.
Quit system-config-nfs and restart the server: /etc/rc.d/init.d/nfs
restart.
Still on the server side, open up in the firewall the ports 2049, 111 and
the ports you used in system-config-nfs (in my example 4000-4003). Both
tcp and udp.
On the client side just install and run autofs. Then, from any client
cd /net/lion/pub
and you're there. No need for cryptic mount commands in /etc/fstab
(although, of course, you can go that way too, if you want). The
automounter will do the work for you, on demand.
Diagnostic: on the client, as root:
showmount -e lion
You should see the partitions you are exporting.
rpcinfo -p lion
You should see which ports the nfs daemons are running on.
The most likely problems are always the firewall and/or improper server
configuration.
If push come to shove, use wireshark to see the traffic between the
client and the server.
More information about the users
mailing list