ns83820 bug. [was Re: Poor NFS client performance on 2.4.18?]

[Dan Yocum <yocum@fnal.gov>]

Trond, et al.

You're right, it's a driver (ns83820) issue.  Strange that it only shows up
when trying to execute an app that's mounted via NFS, but, whatever. 
Running apps from the the NFS volumes with the eepro100 adapter that's on
the machine works fine with the updated NFS_all patch applied.

Thanks, again,
Dan


Dan Yocum wrote:
> 
> 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.