On 03/03/13 01:56, Ben Hutchings wrote:
Control: tag -1 moreinfo fixed-upstream
On Thu, 2013-02-28 at 15:28 +0000, Chris Boot wrote:
We are also seeing this on an NFS server hosing home directories for a
fairly large deployment of Debian desktop systems. The symptoms and perf
top agree perfectly with what the reporter is experiencing.
Please consider backporting said patch to the 3.2 kernel for
wheezy/squeeze-backports.
Please test the attached backport as explained here:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
Hi Ben,
I have been testing a 3.2 kernel with both the patch you backported as
well as 64a284d07c7d84299a90826950079a8ef11e8204 from upstream ("nfsd4:
maintain one seqid stream per (lockowner, file)"). These patches
together appear to have resolved the issues our client has been seeing,
though this is not running in a production environment just yet.
I think the other patch (64a284d07c7d84299a90826950079a8ef11e8204) is
also quite important in resolving this problem, as it reduces the number
of entries in the lockowner hash table. Would this be a patch you would
entertain to backport as well?