05-26-2011
If it's SAN issue, you should check if multipath is configured for the mountpoint / disk[s] failing.
Perhaps administrator forgot to configure path, one of your FC cards died and it cannot see LUN(S) used for this mountpoint.
Also check clients, you would want to umount that share from all clients using broken NFS share.
Is there anything in syslog ?
Basicely, NFS issues are visible clearly in the client's syslog and disk problems should be on server's syslog.
Using open source solutions (or your scripts) you can parse those logs on multiple servers and create notifications and such (email, web or whatever).
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
i am using HPUX11.00 and i am facing a starnge problem
after some time when i log on a message is coimng
NFS server not responding still trying....and it keps on coming there is no other way but to log out..form the server and start once again...
there is no file system exported or NFS... (3 Replies)
Discussion started by: Prafulla
3 Replies
2. UNIX for Dummies Questions & Answers
I'm in panic mode. This isn't a production server, however, is very vital to office.
Sun V240 with Solaris 9, stopped accepting ftp sessions. When I tried to remote into box, it didn't respond. I have tried rebooting to boot in single user mode, no luck. I can see that it is ON but I can't get it... (3 Replies)
Discussion started by: mkeis1144
3 Replies
3. Solaris
At times I have unknown applications that hang for long periods of time over and over again after a network glitch. These are sometimes nfs4 but usually nfs3 clients and are always solaris10 systems.
nfs: NFS server hostname not responding still trying
nfs: NFS server hostname ok
nfs: NFS... (1 Reply)
Discussion started by: HPAVC
1 Replies
4. Solaris
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
5. Red Hat
Greetings!
I'm testing a failover solution for NFSv4 on RHEL6 with latest updates.
My script umounts (umount -lf /share) the faulty NFS share if it sees that's hanging on the client (the NFS daemon is down on the NFS server) and it mounts the share from another healthy NFS server.
Sometimes... (4 Replies)
Discussion started by: Arsene Lupen
4 Replies
6. Red Hat
I have RHEL5 server
Sometimes ping timeout occured and i can not access server from any tool
or ILOM
Any ideas how to solve this? (5 Replies)
Discussion started by: rafat_nasar2010
5 Replies
7. UNIX for Dummies Questions & Answers
Server is accessible only via IPMI. SSH and web control panel is timeout. Takes several hours. Server dont have high load or suspicious processes.
I checked /etc/hosts.deny and restarted ssh, but nothing :( (0 Replies)
Discussion started by: postcd
0 Replies
8. AIX
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
9. UNIX for Beginners Questions & Answers
Hello,
I got the below error on my AIX system when doing a df command
NFS server xxx not responding still trying
We check and know that the NFS server is not available anymore. So we would like to unmount it, but no help.
/ > umount /mountpoint/
umount: Could not find anything to... (4 Replies)
Discussion started by: Phat
4 Replies
LEARN ABOUT SUSE
rpc.nfsd
rpc.nfsd(8) System Manager's Manual rpc.nfsd(8)
NAME
rpc.nfsd - NFS server process
SYNOPSIS
/usr/sbin/rpc.nfsd [options] nproc
DESCRIPTION
The rpc.nfsd program implements the user level part of the NFS service. The main functionality is handled by the nfsd kernel module. The
user space program merely specifies what sort of sockets the kernel service should listen on, what NFS versions it should support, and how
many kernel threads it should use.
The rpc.mountd server provides an ancillary service needed to satisfy mount requests by NFS clients.
OPTIONS
-d or --debug
enable logging of debugging messages
-H or --host hostname
specify a particular hostname (or address) that NFS requests will be accepted on. By default, rpc.nfsd will accept NFS requests on
all known network addresses. Note that lockd (which performs file locking services for NFS) may still accept request on all known
network addresses. This may change in future releases of the Linux Kernel.
-p or --port port
specify a diferent port to listen on for NFS requests. By default, rpc.nfsd will listen on port 2049.
-N or --no-nfs-version vers
This option can be used to request that rpc.nfsd does not offer certain versions of NFS. The current version of rpc.nfsd can support
both NFS version 2,3 and the newer version 4.
-s or --syslog
By default, rpc.nfsd logs error messages (and debug messages, if enabled) to stderr. This option makes rpc.nfsd log these messages
to syslog instead. Note that errors encountered during option processing will still be logged to stderr regardless of this option.
-T or --no-tcp
Disable rpc.nfsd from accepting TCP connections from clients.
-U or --no-udp
Disable rpc.nfsd from accepting UDP connections from clients.
nproc specify the number of NFS server threads. By default, just one thread is started. However, for optimum performance several threads
should be used. The actual figure depends on the number of and the work load created by the NFS clients, but a useful starting point
is 8 threads. Effects of modifying that number can be checked using the nfsstat(8) program.
Note that if the NFS server is already running, then the options for specifying host, port, and protocol will be ignored. The number of
processes given will be the only option considered, and the number of active nfsd processes will be increased or decreased to match this
number. In particular rpc.nfsd 0 will stop all threads and thus close any open connections.
NOTES
If the program is built with TI-RPC support, it will enable any protocol and address family combinations that are marked visible in the
netconfig database.
SEE ALSO
rpc.mountd(8), exports(5), exportfs(8), rpc.rquotad(8), nfsstat(8), netconfig(5).
AUTHOR
Olaf Kirch, Bill Hawes, H. J. Lu, G. Allan Morris III, and a host of others.
7 Aug 2006 rpc.nfsd(8)