On Wed, Nov 25, 2009 at 15:31, Trond Myklebust
<trond.myklebust@xxxxxxxxxx> wrote:
> On Wed, 2009-11-25 at 09:56 +0100, Stephen R. van den Berg wrote:
>> The kernel hangs at this point, the only way to get out of there is
>> using SysBreak.
> This just means that the RPC client is waiting for a reply from the NFS
> server.
Even if it is, I'd say that the kernel has no business "busywaiting"
for that response. It should yield to other processes. So even if
the response does get lost, the kernel shouldn't become locked.
> Does 'netstat -t' show that there is an active TCP connection to the
> server's nfs port?
> Does wireshark show that the client should have received a reply?
I'll do a packettrace and let you know.
--
Sincerely,
Stephen R. van den Berg.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
