[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-stable
Subject:    Re: NFSv3 seriously broken in 3.1
From:       Gerald Pfeifer <pfeifer () dbai ! tuwien ! ac ! at>
Date:       1999-06-30 14:50:58
[Download RAW message or body]

On Mon, 28 Jun 1999, David O'Brien wrote:
>> Just to make sure, there has been no change between FreeBSD 3.1 and 3.2,
>> right?
> 3.1 defaulted to v3/TCP.  3.2 defaults to v3/UDP (or at least should).
> HOWEVER /etc/amd.map specifies v2/UDP.
> 
> Are you able to use ``snoop -v'' on a Sun to verify the protocols used?
> (or tcpdump if you don't have Solaris)

Yes. I checked with `snoop -v` and indeed I only saw NFS2 requests going
over the wire from that specific FreeBSD box.

In addition to our AMD maps we statically mount /var/mail; either without
any options or when forced to v2/UDP, a 3.2 client hangs now and then when
sending mail from Pine.

Finally, please note that we are on an extremely bad network with ~10%
Ethernet collisions.


Perhaps a history might be helpful?

 1. 2.2.x clients against a SunOS 4.x host. No problems.
 2. 2.2.x clients against a Solaris 2.6 host. No problems.
 3. 3.1 clients have long hangs now and then; sending mail with Pine hangs
    forever now and then. 2.2.x clients are fine.
 4. Force v2/UDP for all AMD maps. Both 2.2.x and 3.1 clients are fine.
 5. 3.2 clients experience infinite hangs when sending mail with Pine now
    and then, all others are fine.
 6. Force v2/UDP for /var/mail on 3.2 client. No change.


Frankly, I feel lost. :-(  Any suggestions what I could try?

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

[prev in list] [next in list] [prev in thread] [next in thread]