From: "Burjan Gabor" <buga+dated+1013026971.2270df@elte.hu>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.4.17 NFS hangup
Date: Sun, 3 Feb 2002 21:22:51 +0100 [thread overview]
Message-ID: <20020203202251.GA22797@csoma.elte.hu> (raw)
Hello,
I have a reproducable problem with 2.4.17 kernel and NFS client after
netbooting an RS/6000 (ppc architecture).
Immediately after boot:
partvis:/tmp# dd if=/dev/zero of=blah1 count=1
1+0 records in
1+0 records out
partvis:/tmp#
partvis:/tmp# dd if=/dev/zero of=blah2 count=2
2+0 records in
2+0 records out
nfs: server 157.181.150.31 not responding, still trying
nfs: server 157.181.150.31 not responding, still trying
nfs: task 913 can't get a request slot
... and so on
Relevant tcpdump output:
20:41:40.927855 heron.elte.hu.nfs > partvis.elte.hu.3648238371: reply ok 28 lookup ERROR: No such file or directory (DF)
20:41:40.928622 partvis.elte.hu.3648238372 > heron.elte.hu.nfs: 148 create [|nfs] (DF)
20:41:40.929271 heron.elte.hu.nfs > partvis.elte.hu.3648238372: reply ok 128 create [|nfs] (DF)
20:41:40.930655 partvis.elte.hu.3648238373 > heron.elte.hu.nfs: 100 getattr [|nfs] (DF)
20:41:40.930976 heron.elte.hu.nfs > partvis.elte.hu.3648238373: reply ok 96 getattr REG 100644 ids 0
However, reading works without any problems. Full tcpdump output from
poweron: http://www.csoma.elte.hu/~burjang/nfs-tcpdump-20010203.out.gz
buga
next reply other threads:[~2002-02-03 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 20:22 Burjan Gabor [this message]
2002-02-03 21:06 ` 2.4.17 NFS hangup Trond Myklebust
2002-02-03 21:34 ` Burján Gábor
2002-02-03 21:58 ` Alan Cox
2002-02-03 22:44 ` Trond Myklebust
2002-02-03 23:00 ` Burján Gábor
2002-02-04 13:21 ` Athanasius
2002-02-04 14:47 ` Athanasius
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=20020203202251.GA22797@csoma.elte.hu \
--to=buga+dated+1013026971.2270df@elte.hu \
--cc=linux-kernel@vger.kernel.org \
/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