public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <ken@canit.se>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nfs problem 2.4.19-pre9
Date: 01 Jun 2002 21:39:21 +0200	[thread overview]
Message-ID: <1022960361.1185.46.camel@tiger> (raw)
In-Reply-To: <shs8z5yrf2v.fsf@charged.uio.no>

On Sat, 2002-06-01 at 21:09, Trond Myklebust wrote:
> >>>>> " " == Kenneth Johansson <ken@canit.se> writes:
> 
>      > I have had a problem for some time that processes get stuck in
>      > D state and I now have a way to get this to happen at will.
> 
>      > One way to do this is to copy a file from one nfs mounted
>      > directory to another. It dose not happen on the same mount and
>      > not when copying from nfs to a local disk. To make this even
>      > more complex it works with cp and mv but not in mc(midnight
>      > commander F6 ).
> 
> Sounds like a network driver problem or something like that. UDP
> appears to trigger these lockups a lot more easily than does TCP.
> 
> Try testing with a different brand of networking card...
> 

I have three cards but they are all the same :(
3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30).

Also Why only this nfs mount. I can still telnet to other computers and
use nfs on another mount point so it's not like I lose the network.






  reply	other threads:[~2002-06-01 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01 14:02 nfs problem 2.4.19-pre9 Kenneth Johansson
2002-06-01 19:09 ` Trond Myklebust
2002-06-01 19:39   ` Kenneth Johansson [this message]
2002-06-01 19:50     ` Trond Myklebust
2002-06-01 20:10       ` Kenneth Johansson
2002-06-02 10:52         ` 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=1022960361.1185.46.camel@tiger \
    --to=ken@canit.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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