What is the best approach when an nfs mount hangs on a client but the
server is OK? I have mount options of:
rw,bg,soft,intr,rsize=32768,wsize=32768
but whatever it did was not interruptable and would not shut down.
There were some:
Oct 15 09:08:32 dev-ngf-l-01 kernel: INFO: task gnome-settings-:19169
blocked for more than 120 seconds.
Oct 15 09:08:32 dev-ngf-l-01 kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
messages on the console and /var/log/messages.
Is this a bug or there a way to avoid it?
--
Les Mikesell
lesmikesell at gmail.com
On 2013-10-15 7:01 PM, Les Mikesell wrote:> but whatever it did was not interruptable and would not shut down. >You don't happen to be using jumbo frames over gigabit, are you?
Did you also check /var/log/messages on the nfs server side ? I had some NFS troubles with lockd some times ago and it was a firewall problem on the client: Try: - log on the NFS server and check in /var/log/messages which client is responsible for the problem (it could be an other one than your client). - on this client stop iptables (service iptables stop) and check if the problem still exist. In my configs, client iptables fully trust my NFS server. Patrick -- ==================================================================| Equipe M.O.S.T. | | | Patrick BEGOU | mailto:Patrick.Begou at grenoble-inp.fr | | LEGI | | | BP 53 X | Tel 04 76 82 51 35 | | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 | ===================================================================