All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: David Chow <davidchow@rcn.com.hk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: nfsroot dead slow with redhat 7.2
Date: Thu, 20 Dec 2001 03:39:39 +0100	[thread overview]
Message-ID: <15393.20331.862567.47007@charged.uio.no> (raw)
In-Reply-To: <1008812943.16827.1.camel@star9.planet.rcn.com.hk>
In-Reply-To: <3C2131FC.6040209@rcn.com.hk> <shs6672n25h.fsf@charged.uio.no> <1008812943.16827.1.camel@star9.planet.rcn.com.hk>

>>>>> " " == David Chow <davidchow@rcn.com.hk> writes:

     > The network is fine. It is so slow that an ls -l at the rootfs
     > takes more than 2 minutes. The readdir() seems alright because
     > the ls immediate counts the number of records says "total
     > blahbalh" but when doing individual lookup calls, it seems slow
     > like hell. We have other production i686smp servers 2.4.14

As I said: 'tcpdump' ought to show you what is going on.

     > serving diskless i686 clients using
     > 2.4.13 kernels works great. Is there any difference in nfsroot
     >        with
     > normal nfsmounts? And can we configure the nfsroot use a v3

Nope: no differences. NFSroot uses the exact same code as standard
NFS.

     > mount?  becaus now it defaults to v2 always.

As I said in my previous mail: use the mount option 'v3' on the kernel
boot line if you want NFSv3.

 e.g. nfsroot="10.0.0.1:/bar,v3"

Cheers,
   Trond

  parent reply	other threads:[~2001-12-20  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20  0:34 nfsroot dead slow with redhat 7.2 David Chow
2001-12-20  0:52 ` Trond Myklebust
2001-12-20  1:49   ` David Chow
2001-12-20  1:58     ` Dax Kelson
2001-12-20  2:39     ` Trond Myklebust [this message]
2001-12-20  8:18       ` David Chow
2001-12-20 11:15         ` Trond Myklebust
2001-12-20 19:43         ` Dax Kelson

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=15393.20331.862567.47007@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=davidchow@rcn.com.hk \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.