Linux NFS development
 help / color / mirror / Atom feed
From: Razvan Gavril <razvan.g@plutohome.com>
To: Manish RATHI <manish.rathi@st.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Nfs problem on target
Date: Mon, 24 Jul 2006 10:42:33 +0300	[thread overview]
Message-ID: <44C479E9.307@plutohome.com> (raw)
In-Reply-To: <003101c6aee9$64f41a90$802cc70a@dlh.st.com>

Manish RATHI wrote:
> Hi,
> When I use NFS on 2.4.20 kernel running on my target board, there is no problem?
> When I migrate to 2.6.16 and enabled nfs then 
> Whenever I execute an application over nfs which access NFS for
> Reading files, I get frequent prints 
> "nfs : server 10.199.3.88 not responding, still trying"
> " nfs : server 10.199.3.88 OK"
>
> On FAQ it's written this can be because of 
> Network congestion 
> Overloaded server 
> Packets (input or output) dropped by a bad NIC or driver.... 
>
> But this problem is not with 2.4 kernel. 
>
> Thanks
> Regards
> Manish
>
>   
I have similar problems when using 2.6.16 on the server :( and using a 
single client who is doing a cp.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2006-07-24  7:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24  6:21 Nfs problem on target Manish RATHI
2006-07-24  7:42 ` Razvan Gavril [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=44C479E9.307@plutohome.com \
    --to=razvan.g@plutohome.com \
    --cc=manish.rathi@st.com \
    --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