The default is to do a hard-mount of NFS shares. Hardmounts hang when the
server disappears. This is... Generally what you will want. adding the
intr option should allow the processes to be killed (but I have not tried
this)
>now, the load goes up and when I came home it was at 144 already. I
>stopped cron, unable to kill off the mrtg calls. I then re-established the
>nfs connection by rebooting the windows back to linux; I then could umount
>the nfs shares and guess what happened -- all DN processes went ayway and
>the system load back to normal.
Count yourself lucky. I was foolishly serving webpages from an NFS
mount. Fortunately apache has limits. Seeing a loadavg in the the hundreds
is... disturbing.
The loadavg does this because processes in the D state get counted wether
they are doing anything or not. I don't know if this is correct or not, but
most unicies seem to do this.
>it seems that some things block in the kernel when the nfs stuff is
>failed. is this right ? is my setup incorrect or what ?
Not incorrect, but you might experiment with soft mounts, which will rapidly
timeout and die with io-errors rather than hanging.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/