From: Sven Geggus <sven@gegg.us>
To: nfs@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: 2.4.21: NFS client Freeze
Date: Tue, 24 Jun 2003 12:12:27 +0200 [thread overview]
Message-ID: <20030624101227.GA21744@benzin.geggus.net> (raw)
Hi there,
After mounting an NFS-Volume exported from a Windows Machine
(Hummingbird-NFS Maestro Server) a simple ls of the mount point causes an
almost complete freeze of the system (ping does still work, but nothing
else).
This did work fine in 2.4.20 but does not work on 2.4.21 anymore!
Here is the debug output I produced using:
echo 3 >/proc/sys/sunrpc/rpc_debug
echo 3 >/proc/sys/sunrpc/nfs_debug
RPC: 24 call_start nfs3 proc 1 (sync)
RPC: 24 call_reserve
RPC: 24 reserved req df16d078 xid 81c60017
RPC: 24 xprt_reserve returns 0
RPC: 24 call_reserveresult (status 0)
RPC: 24 call_allocate (status 0)
RPC: 24 call_encode (status 0)
RPC: 24 call_transmit (status 0)
RPC: 24 xprt_transmit(81c60017)
RPC: 24 xprt_cwnd_limited cong = 0 cwnd = 512
RPC: xprt_sendmsg(0) = 108
RPC: udp_data_ready...
RPC: udp_data_ready client df16d000
RPC: 24 received reply
RPC: cong 256, cwnd was 512, now 512
RPC: 24 has input (112 bytes)
RPC: 24 xmit complete
RPC: 24 call_status (status 112)
RPC: 24 call_decode (status 112)
RPC: 24 call_decode result 0
RPC: 24 release request df16d078
RPC: rpc_release_client(dfd6b480, 2)
NFS: refresh_inode(7/395120 ct=1 info=0x6)
RPC: 25 call_start nfs3 proc 4 (sync)
RPC: 25 call_reserve
RPC: 25 reserved req df16d078 xid 81c60018
RPC: 25 xprt_reserve returns 0
RPC: 25 call_reserveresult (status 0)
RPC: 25 call_allocate (status 0)
RPC: 25 call_encode (status 0)
RPC: 25 call_transmit (status 0)
RPC: 25 xprt_transmit(81c60018)
RPC: 25 xprt_cwnd_limited cong = 0 cwnd = 512
RPC: xprt_sendmsg(0) = 112
RPC: 25 xmit complete
RPC: udp_data_ready...
RPC: udp_data_ready client df16d000
RPC: 25 received reply
RPC: cong 256, cwnd was 512, now 512
RPC: 25 has input (36 bytes)
RPC: 25 call_status (status 36)
RPC: 25 call_decode (status 36)
RPC: 25 call_decode result 0
RPC: 25 release request df16d078
RPC: rpc_release_client(dfd6b480, 2)
NFS: readdir_search_pagecache() searching for cookie 0
NFS: find_dirent_page() searching directory page 0
NFS: nfs_readdir_filler() reading cookie 0 into page 0.
RPC: 26 call_start nfs3 proc 16 (sync)
RPC: 26 call_reserve
RPC: 26 reserved req df16d078 xid 81c60019
RPC: 26 xprt_reserve returns 0
RPC: 26 call_reserveresult (status 0)
RPC: 26 call_allocate (status 0)
RPC: 26 call_encode (status 0)
RPC: 26 call_transmit (status 0)
RPC: 26 xprt_transmit(81c60019)
RPC: 26 xprt_cwnd_limited cong = 0 cwnd = 512
RPC: xprt_sendmsg(0) = 128
RPC: 26 xmit complete
RPC: udp_data_ready...
RPC: udp_data_ready client df16d000
RPC: 26 received reply
RPC: cong 256, cwnd was 512, now 512
RPC: 26 has input (760 bytes)
RPC: 26 call_status (status 760)
RPC: 26 call_decode (status 760)
Regards
Sven
--
.. this message has been created using an outdated OS (UNIX-like) with an
outdated mail- or newsreader (text-only) :-P
/me is giggls@ircnet, http://sven.gegg.us/ on the Web
next reply other threads:[~2003-06-24 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 10:12 Sven Geggus [this message]
2003-06-24 18:55 ` Trond Myklebust
2003-06-25 8:05 ` PROBLEM: reproduceable 2.4.21 " Sven Geggus
2003-06-27 7:44 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030624101227.GA21744@benzin.geggus.net \
--to=sven@gegg.us \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®