Messages in this thread | | | Subject | Re: 2.2.1 SMP: NFS can't get a request slot | From | Trond Myklebust <> | Date | 23 Feb 1999 12:10:19 +0100 |
| |
Steve Hsieh <steveh@eecs.umich.edu> writes:
> Can someone explain what this message means? > > Feb 4 08:51:15 sk kernel: nfs: task 31658 can't get a request slot > Feb 4 08:51:41 sk kernel: nfs: task 31659 can't get a request slot > Feb 4 08:51:49 sk kernel: nfs: task 31660 can't get a request slot > > After seeing these messages, nfs on this SMP 2.2.1 machine no longer > works. The problem only seems to crop up if the machine accesses its own > nfs server (ie: export a directory and then access the directory via amd's > automounter on the same machine). >
The messages themselves just mean that the RPC layer is congested, and that a backlog of messages waiting to be sent is building up. Whenever one of these messages times out, it issues the 'task xxx can't get a request slot' error.
The question then arises as to why the RPC layer gets congested when accessing your own nfs server. I have no problems with this on my own machine, so I would first and foremost suspect amd. Can you repeat the problem using just the stock NFS client + server?
Cheers, Trond
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |