From: Dan Yocum <yocum@fnal.gov>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Poor NFS client performance on 2.4.18?
Date: Tue, 07 May 2002 10:54:10 -0500 [thread overview]
Message-ID: <3CD7F8A2.24DF8433@fnal.gov> (raw)
In-Reply-To: <3CC86BDC.C8784EA2@fnal.gov> <shsu1pyppnz.fsf@charged.uio.no> <3CD6FE1E.A20384D@fnal.gov> <E174zP0-0007N9-00@charged.uio.no> <3CD7F385.BAA3870B@fnal.gov>
Dan Yocum wrote:
>
> Trond Myklebust wrote:
> >
> > On Tuesday 7. May 2002 00:05, Dan Yocum wrote:
> > > Trond,
> > >
> > > OK, so backing out the rpc_tweaks dif fixed the performance problem,
> > > however, seems to have introduced another problem that appears to be
> > > stemming from the seekdir.dif. Attempting to run an app from an IRIX
> > > client (that has the 32bitclients option set) freezes the NFS volume - one
> > > can't access it from the Linux side, anymore.
> > >
> > > You can read and write to the NFS volume *before* trying to run something
> > > from there, but not after.
> > >
> > > Ideas?
> >
> > That smells like another network driver bug. Have you tcpdumped the traffic
> > between client and server?
>
> Ah, that may be the case - the problem also exists with a Linux server as
> well... let me check, and I'll let you know.
I take that back - it's only hanging on the Linux server when the IRIX
server is already hung.
--
Dan Yocum
Sloan Digital Sky Survey, Fermilab 630.840.6509
yocum@fnal.gov, http://www.sdss.org
SDSS. Mapping the Universe.
next prev parent reply other threads:[~2002-05-07 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 20:49 Poor NFS client performance on 2.4.18? Dan Yocum
2002-04-26 13:14 ` Trond Myklebust
2002-04-26 14:51 ` Dan Yocum
2002-04-28 19:29 ` Trond Myklebust
2002-05-06 22:05 ` Dan Yocum
2002-05-07 7:28 ` Trond Myklebust
2002-05-07 15:32 ` Dan Yocum
2002-05-07 15:54 ` Dan Yocum [this message]
2002-05-08 20:19 ` ns83820 bug. [was Re: Poor NFS client performance on 2.4.18?] Dan Yocum
2002-05-08 22:07 ` Benjamin LaHaise
2002-05-09 20:54 ` Dan Yocum
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=3CD7F8A2.24DF8433@fnal.gov \
--to=yocum@fnal.gov \
--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