public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wouter Vlothuizen <maillists@vlothuizen.nl>
To: Joshua Weage <weage98@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS client problems in 2.4.18 to 2.4.20
Date: Wed, 10 Sep 2003 20:37:29 +0200	[thread overview]
Message-ID: <3F5F6F69.CD851A2F@vlothuizen.nl> (raw)
In-Reply-To: 20030906162949.27200.qmail@web40405.mail.yahoo.com

Joshua Weage wrote:
> 
> has stopped working?  I've looked at nfsstat and the kernel seems to
> have stopped sending any data to the server, or it may send one packet
> every couple of seconds.  If I start up another shell and try to do an
> ls on the problem filesystem, the command locks up and can't be
> interrupted.  I think I've also mounted the same filesystem in another
> location, on the same machine, and it works fine.
> 

I am experiencing similar problems with 2.4.18 as a client (the NFS
server is on Solaris). When the client freezes I see nfsstat 'client rpc
retrans' counting fast. I found a quite strange way to unlock the
machine, by performing a port scan with nmap from elsewhere.
BTW, which Gigabit ethernet do you use, I use tg3, there could be a
relation to the network card?

Cheers,
Wouter

      parent reply	other threads:[~2003-09-10 18:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05 20:44 NFS client problems in 2.4.18 to 2.4.20 Joshua Weage
2003-09-05 21:51 ` Trond Myklebust
2003-09-06 16:29   ` Joshua Weage
2003-09-06 17:09     ` Trond Myklebust
2003-09-06 21:22       ` Joshua Weage
2003-09-06 23:14         ` Jamie Lokier
2003-09-07  1:54           ` Trond Myklebust
2003-09-07  2:02           ` Trond Myklebust
2003-09-07 14:27             ` Jamie Lokier
2003-09-07 15:18               ` Trond Myklebust
2003-09-07 15:42                 ` Jamie Lokier
2003-09-07 16:03                   ` Trond Myklebust
2003-09-10 18:37     ` Wouter Vlothuizen [this message]

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=3F5F6F69.CD851A2F@vlothuizen.nl \
    --to=maillists@vlothuizen.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weage98@yahoo.com \
    /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