From: Luis Henriques <luis.henriques@canonical.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Regretion on NFS in mainline kernel
Date: Wed, 18 Apr 2012 12:26:10 +0100 [thread overview]
Message-ID: <20120418112610.GA3979@zeus> (raw)
Hi,
We have a bug reporting a regression in mainline kernel. Basically, the
bug reporters are seeing lots of messages:
[ 48.701213] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
[ 48.701990] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
[ 53.696076] nfs4_reclaim_open_state: 6440 callbacks suppressed
This happens when mounting a user's home directory over NFS.
Is this a known issue being addressed at the moment? Is there any
information needed to help debugging the issue?
The original bug report can be found here:
http://bugs.launchpad.net/bugs/974664
And there's also a similar report for Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=811138
Cheers,
--
Luis
next reply other threads:[~2012-04-18 11:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 11:26 Luis Henriques [this message]
2012-04-18 13:28 ` Regretion on NFS in mainline kernel Jeff Layton
2012-04-18 13:57 ` Luis Henriques
2012-04-18 14:04 ` Myklebust, Trond
2012-04-18 14:13 ` Luis Henriques
2012-04-18 14:15 ` Jeff Layton
2012-04-18 14:41 ` Myklebust, Trond
2012-04-18 14:51 ` Jeff Layton
2012-04-18 17:35 ` Luis Henriques
2012-04-18 17:36 ` [PATCH 0/2] Fix regression " Trond Myklebust
2012-04-18 17:42 ` Jeff Layton
2012-04-18 17:50 ` Luis Henriques
2012-04-19 9:30 ` Luis Henriques
2012-04-19 13:48 ` Luis Henriques
2012-04-19 17:29 ` Myklebust, Trond
2012-04-19 20:46 ` Luis Henriques
2013-01-04 10:05 ` Mario Bachmann
2013-01-04 14:15 ` Myklebust, Trond
2013-01-06 10:48 ` Mario Bachmann
2012-04-18 17:36 ` [PATCH 1/2] NFSv4: Ensure that the LOCK code sets exception->inode Trond Myklebust
2012-04-18 17:36 ` [PATCH 2/2] NFSv4: Ensure that we check lock exclusive/shared type against open modes Trond Myklebust
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=20120418112610.GA3979@zeus \
--to=luis.henriques@canonical.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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.