On Fri, Aug 06, 2004 at 08:11:53AM +0100, Niall O Broin mentioned:
> Specifically, why is that that when a server disappears, the clients
> get stale NFS file handles even when the server has come back? A key
> point of NFS is its clientside statelessness. Of course, this is how it
> has worked on Sun boxes since forever - an NFS server could go away,
> and the client would work away happily, and would carry on where it
> left off whenever the server came back. I won't be surprised to be
> told that Linux has "improved" NFS so that this is no longer true, but
> I hope somebody will be able to tell me how to unimprove it so that I
> don't screw upp all my NFS clients when I need to reboot the server.
Would you believe, I was asking my self the same question just this
morning. I came in this morning to see that for the second time in a few
weeks, an NFS server had a tar process, and half a dozen nfsd processes in
D state. The machine needed a restart (hard power off) before it'd work,
as the processes refused to die, and hung the "killall" that's usually run
on shutdown.
The tar was run on the NFS server, as a local process. I've a nasty
feeling it's an interaction between XFS and NFS. I've even seen "ls" hang
when run on the NFS server in a shared folder.
john
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
