NFS - IP bind

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat NFS - IP bind
# 1  
Old 09-08-2009
NFS - IP bind

Hello,

Our production linux server have multiple network interface.
Recently we installed and started NFS. Now the client server cannot mount to the server running NFS.

Later it was discovered that the port being used for NFS is only bound to one IP address, which is not the IP address I want.

Is it possible to have NFS listen on the IP that I want or listen on all IP addresses?

Thanks,
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

NFS write error on host xyz: Stale NFS file handle - Solaris 10

Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400) Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 Replies

2. UNIX for Advanced & Expert Users

Bind

Hi All I need to do bind of exiting filesystem to new storage allocated mount --bind /prod/OpenCSS /var/lib/test echo "/prod/OpenCSS /var/lib/pgsql bind bind 0 0" >> /etc/fstab will this command just work ? (2 Replies)
Discussion started by: anil529
2 Replies

3. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

4. AIX

AIX NFS Server and NFS Client

Hi 2 ALL, try to run NFS Server in AIX 7.1 : 1. Step by step on NFS Server node mkdir /tmp/test chgrp staff /tmp/test chmod 775 /tmp/test-- create export directory (fs) mknfsexp -d /tmp/test -t ro exportfs -va show mount -e :/# exportfs -av exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies

5. Solaris

Window NFS VS Solaris NFS

Hi all, currently i wish to build a NFS server (windows based), is it the I/O speed will slower than the NFS server in Solaris? any impact, i using the NFS in windows? (2 Replies)
Discussion started by: SmartAntz
2 Replies

6. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

7. Solaris

All dependicies of nfs service is online but nfs is offline

Hi all in my server all nfs dependices are online but nfs client is offline root@BIWAPP1 # svcs -a|grep nfs disabled Sep_05 svc:/network/nfs/server:default online Sep_05 svc:/network/nfs/rquota:default online Sep_05 svc:/network/nfs/mapid:default online ... (9 Replies)
Discussion started by: spandhan
9 Replies

8. Red Hat

bind nfs service to nic

Hello everyone, I am running a RHEL4 server. We have 4 nics, which are paired to create bond0 and bond1. BOND0 is on a vlan which can see our storage system. BOND1 cannot see the storage system. I would like to lock down the system, so that NFS share can only mounted via BOND0. Has anyone done... (2 Replies)
Discussion started by: vada010
2 Replies

9. Solaris

NFS write error on host : Stale NFS file handle

:confused:Hi all When i see in the /var/adm/messages, i saw the following error unix: NFS write error on host : Stale NFS file handle. unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49) It is using sunOS 5.7. Is anybody know what is this error? Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies
Login or Register to Ask a Question
nfsd(8) 						      System Manager's Manual							   nfsd(8)

NAME
nfsd - The remote NFS compatible server SYNOPSIS
/usr/sbin/nfsd [-t num_tcpthreads] [-u num_udpthreads] The following form of the nfsd command is not recommended and is supported only for backward compatibility: /usr/sbin/nfsd [numthreads] FLAGS
Specifies a number of TCP server threads (per RAD) to spawn. A value of 8 is recommended as a start. Specifies a number of UDP server threads (per RAD) to spawn. A value of 8 is recommended as a start. DESCRIPTION
The nfsd daemon runs on a server machine to service NFS requests from client machines. The daemon spawns a number of server threads that process NFS requests from client machines. At least one server thread must be running for a machine to operate as a server. There are two types of server threads: a server thread that processes NFS requests sent using TCP and a server thread that processes NFS requests sent using UDP. This is necessary because the kernel paths for UDP and TCP NFS messages are different. The -t option specifies the number of TCP threads to run and the -u option specifies the number of UDP threads to run. On systems that support Cache Coherent NUMA, the number of threads is per Resource Affinity Domain (RAD). As you add RADs, the NFS server will automatically scale by creating additional threads. NFS requests are processed by a particular RAD based on the file being accessed; this confines cached information about a file to a single RAD for efficiency. See numa_intro(3) for more information on the NUMA architec- ture. If you use the SysMan Menu to configure NFS, it sets the default at 8 UDP and 8 TCP threads. However, a user can have any number of TCP and UDP nfsd threads running up to a maximum of 128 threads. The optimal number of TCP server threads and UDP server threads depends on many factors. See nfsiod(8) for more information. The server threads are implemented as kernel threads; they are part of Process ID 0, not the nfsd process. The ps axml command displays idle server threads under PID 0. Idle threads will be waiting on nfs_udp_wait or nfs_tcp_wait. Therefore, if 16 server threads are config- ured, only one nfsd process is displayed in the output from the ps command, although 16 server threads are available to handle NFS requests. Files that are larger than 2 gigabytes are exported as 2 gigabyte files when accessed by NFS Version 2. NFS Version 2 is a 32-bit proto- col, therefore, the size and offset fields are 32-bit quantities (on Alpha UFS they are 64-bit quantities). Use caution when accessing files larger than 2 gigabytes from NFS clients. EXAMPLES
In the following example, 16 threads are run (8 for TCP and 8 for UDP): nfsd -t 8 -u 8 FILES
Specifies the command path Specifies the file for logging startup errors (before the server threads are started). Specifies the file for logging NFS errors (after the server threads are started). RELATED INFORMATION
Commands: mount(8), mountd(8), nfsconfig(8), nfsstat(8), portmap(8) System calls: nfssvc(2) delim off nfsd(8)