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
Subject: Re: nfsroot dead slow with redhat 7.2
Date: 20 Dec 2001 12:15:53 +0100	[thread overview]
Message-ID: <shsadwef8gm.fsf@charged.uio.no> (raw)
In-Reply-To: <3C2131FC.6040209@rcn.com.hk> <shs6672n25h.fsf@charged.uio.no> <1008812943.16827.1.camel@star9.planet.rcn.com.hk> <15393.20331.862567.47007@charged.uio.no> <1008836323.972.6.camel@star7.planet.rcn.com.hk>
In-Reply-To: <1008836323.972.6.camel@star7.planet.rcn.com.hk>

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

     > Just find out... it is a problem of some settings in /etc
     > directory it is not related to the FSes . I replaced the /etc
     > directory with the one we are using on the production
     > machines... by the way. What can be wrong? When it starts init
     > , and execute the /etc/rc.d/rc.sysinit , it is hell slow. We
     > have tried replace /sbin/init with bash and we got out a shell
     > but "ls -l" takes more than 2 minutes... do you know what sort
     > of settings in the /etc will affect use space "bash" or "glibc"
     > on nfsroot behaves different ? This is so strange.

Anything network related: ipchains, network parameters, ...
Also, if things like portmapper, statd, and the remaining NFS mounts
are getting started in the wrong order.

Cheers,
  Trond

  reply	other threads:[~2001-12-20 11:16 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
2001-12-20  8:18       ` David Chow
2001-12-20 11:15         ` Trond Myklebust [this message]
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=shsadwef8gm.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=davidchow@rcn.com.hk \
    --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.