Dear Trond,
Thanks for answering my question, we have use the i386 kernel at the
server that works fine. Also even we uses the i686 kerenl at the server,
it happens normally when doing NFS mounts, it will only be dead slow
when
server i686 2.4.7-10 kernel && client nfsroot(2.4.13 i686)
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 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 mount?
becaus now it defaults to v2 always.
David
¦b ¶g¥|, 2001-12-20 08:52, Trond Myklebust ¼g¹D¡G
> >>>>> " " == David Chow <davidchow@rcn.com.hk> writes:
>
> > Dear all, When I use 2.4.7-10 i686 kernel from stock Redhat 7.2
> > as the NFS server. My NFS client use the 2.4.13 kernel, when I
> > mount the nfsroot to the server, I found it is dead slow on the
> > client. This only happens in i686 kernel on the server, if we
> > use a K6-2 uses an i386 server its fine. What's going on? By
>
> Usually means you have a bad network connection. Use tcpdump to
> isolate where on the network packets (and UDP fragments) are
> disappearing.
>
> > the way, how to configure the client to default use a NFSv3
> > mount? Thanks.
>
> Specify the 'v3' NFSroot mount option.
>
> Cheers,
> Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:20 EST