benlutz at datacomm.ch
Tue Oct 12 07:54:27 PDT 2004
> > > Are other NFS clients able to continue to access the NFS
> > > server without problems?
> > Partially. Other clients can access parts of the exported share. It
> > appears that as soon as they access the directory in which the first
> > program froze, they freeze as well.
> If you log into the server and try to access that directory, do you
Yes, no problems or slowdowns.
> You talked about having non-FreeBSD 5.x clients as well, I think, in an
> earlier e-mail -- if a FreeBSD 5.x client wedges on a directory on the
> server, will another non-FreeBSD client also wedge on touching the
I'm sorry, I misread the question. What I was trying to say is that other
programs on the same machine that has one program in a freeze can still
access the NFS share, until they access the same directory that the
frozen program is accessing.
Other clients (as in other machines) are totally unaffected.
> Is it always the same director(y/ies) in which the wedge occurs?
Yes, given that I use more or less the same directory to store the files
in that I currently work with. It is more than one directory though, I've
seen this with at least 4 different ones.
> The behavior you describe above sounds like it might be a problem with
> the server, or, that the server generates bad or maybe just different
> responses that trigger a client bug for particular directories or in
> particular circumstances? With the exceptions of things like
> distributed advisory locking (rpc.lockd, etc), bugs in one client won't
> generally trigger the problem in another client a the same time unless
> it's a common property of the directory they touch.
Given that the problem occurs with both a Gentoo machine acting as NFS
server and a FreeBSD 4.10 machine acting as NFS server (the latter has
been working fine since 4.10 was released, and under previous releases
before that), I think those work just fine.
> Ruling out debug.mpsafenet and/or if_re checksum issues would both be
> useful things to do.
I strongly suspect it was the re checksum issue. I've disabled both
debug.mpsafenet and txcsum offloading, and NFS seems to work fine again.
I've copied a few GB of data back and forth, no freezes.
Thanks again for your time.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041012/cf4a9a10/attachment.bin
More information about the freebsd-current