Hi all,

I've got a Solaris 10 u4 x86 machine with a vexing issue. It's an NFS 
client of a v240 running Sol9. It works fine for a few weeks, and then 
seemingly at random, begins to lose contact with the NFS server.

Mount requests, file open/write requests are issued by the client, are 
picked up by the server and are responded to. The network acks make it 
back to the client's NIC (I've got the client hooked to a hub w/ a 
laptop connected via same in promiscuous mode), but snoop on the client 
doesn't show the NFS traffic that I see on the laptop. All other network 
traffic goes through fine. These are hard NFSv3 mounts over TCP.

Sometimes, shutting down NFS client services in SMF and bouncing the 
interface  and/or disconnecting the network cable will fix the issue; in 
any case a reboot always fixes it for up to a month or so.

The NIC is a builtin Intel e1000g, BTW.

Any ideas?

GBA wrote:
> Hi all,
> 
> I've got a Solaris 10 u4 x86 machine with a vexing issue. It's an NFS 
> client of a v240 running Sol9. It works fine for a few weeks, and then 
> seemingly at random, begins to lose contact with the NFS server.
> 
> Mount requests, file open/write requests are issued by the client, are 
> picked up by the server and are responded to. The network acks make it 
> back to the client's NIC (I've got the client hooked to a hub w/ a 
> laptop connected via same in promiscuous mode), but snoop on the client 
> doesn't show the NFS traffic that I see on the laptop. All other network 
> traffic goes through fine. These are hard NFSv3 mounts over TCP.
> 

Bah. I meant UDP. Sorry.

GBA wrote:
> GBA wrote:
>> Hi all,
>>
>> I've got a Solaris 10 u4 x86 machine with a vexing issue. It's an NFS
>> client of a v240 running Sol9. It works fine for a few weeks, and then
>> seemingly at random, begins to lose contact with the NFS server.
>>
>> Mount requests, file open/write requests are issued by the client, are
>> picked up by the server and are responded to. The network acks make it
>> back to the client's NIC (I've got the client hooked to a hub w/ a
>> laptop connected via same in promiscuous mode), but snoop on the
>> client doesn't show the NFS traffic that I see on the laptop. All
>> other network traffic goes through fine. These are hard NFSv3 mounts
>> over TCP.
>>
> 
> Bah. I meant UDP. Sorry.

Why have you used UDP? Can you show us the mount commands you've used?

Thommy M. wrote:
> GBA wrote:
>> GBA wrote:
>>> Hi all,
>>>
>>> I've got a Solaris 10 u4 x86 machine with a vexing issue. It's an NFS
>>> client of a v240 running Sol9. It works fine for a few weeks, and then
>>> seemingly at random, begins to lose contact with the NFS server.
>>>
>>> Mount requests, file open/write requests are issued by the client, are
>>> picked up by the server and are responded to. The network acks make it
>>> back to the client's NIC (I've got the client hooked to a hub w/ a
>>> laptop connected via same in promiscuous mode), but snoop on the
>>> client doesn't show the NFS traffic that I see on the laptop. All
>>> other network traffic goes through fine. These are hard NFSv3 mounts
>>> over TCP.
>>>
>> Bah. I meant UDP. Sorry.
> 
> Why have you used UDP? Can you show us the mount commands you've used?

For example, one of the affected filesystems is mounted read-write, 
background enabled, nosuid and quotas on. UDP was the 
lowest-common-denominator transport for lots of clients, but this one 
could just as easily be switched to TCP.

-GBA