Re: Performance/stability problems with nfs shares

[Dawid Stawiarski <neeo@xl.wp.pl>]

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

W dniu 02.08.2013 17:47, J. Bruce Fields pisze:
> On Fri, Aug 02, 2013 at 04:37:57PM +0200, Dawid Stawiarski wrote:
>> W dniu 02.08.2013 15:12, Jeff Layton pisze:
>>> Typically, a stack trace like that indicates that the process is
>>> waiting for the server to respond. The first thing I would do would be
>>> to ascertain whether the server is actually responding to these
>>> requests.
>>>
>>
>> The same share is accessible on other nodes, so the problem involves
>> only one of the nodes (completly random) at a time.
>
> It's still conceivable that a server problem could cause it to stop
> responding to calls only from a single client--it'd be useful if
> possible to check a trace to see if that's what's happening.  If the
> traffic is really huge then capturing and analyzing a good trace may be
> difficult.

We have almost one hundred NFS nodes, and they're all using the same 
shares with about the same volume of traffic - and only one of the nodes 
at a time has a problem for only one share (other shares from the SAME 
server work OK on the "failing" node) - so it's hard to belive it's the 
server that causes the problem. And yes - with that amount of traffic 
it's hard to make a meaningfull trace on the server side (as noted 
before server is NexentaStor based, and not Linux).

Dawid


[-- Attachment #2: Kryptograficzna sygnatura S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4231 bytes --]