From: "matteo.debiaggi" <matteo.debiaggi@charta.it>
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Cc: Neil Brown <neilb@suse.de>, nfs@lists.sourceforge.net
Subject: Re: Lock problem.
Date: Thu, 11 Oct 2007 16:24:38 +0200 [thread overview]
Message-ID: <470E3226.4080706@charta.it> (raw)
In-Reply-To: <EXNANE011B6gVs1tIzm000006ba@exnane01.hq.netapp.com>
The 2 machines are in a local net without any kind of firewalls ..
But the problem "seems" to be solved :
I think the problem is in lockd daemon.
Explained 30 sec waiting : 2 locks request with default timeout 15 sec..
And then why lock not gained on server? Maybe due to max concurrent
threads asking fo lock to lockd daemon where the default is 20!My test
implyies 2000 lines writing on file with a pause of 10000 us between
write attempt and reading every 100ms.So 20 lock requests queued are a
possible context.
I restarted lockd daemon with 100 as maximum contemporary lock
requests from threads and test goes fine.
Thanks to everybody.
I hope not to face this problem again after this modify.
Matteo.
p.s. i can't get nlm decoding from tcpdump..
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-10-11 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 8:56 Lock problem matteo.debiaggi
2007-10-11 10:08 ` Neil Brown
2007-10-11 13:07 ` matteo.debiaggi
2007-10-11 13:50 ` Talpey, Thomas
2007-10-11 14:24 ` matteo.debiaggi [this message]
2007-10-11 14:37 ` Talpey, Thomas
2007-10-11 15:23 ` matteo.debiaggi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=470E3226.4080706@charta.it \
--to=matteo.debiaggi@charta.it \
--cc=Thomas.Talpey@netapp.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.