Linux NFS development
 help / color / mirror / Atom feed
From: "Paweł Sikora" <pawel.sikora@agmk.net>
To: linux-nfs@vger.kernel.org
Subject: [3.6.11] NFS: Cache request denied due to non-unique superblock keys.
Date: Wed, 19 Dec 2012 19:58:10 +0100	[thread overview]
Message-ID: <6078496.RFsWrNWv86@localhost> (raw)

Hi,

i'm testing the 3.6.11 kernel on some small internal nfs network (1 server <-> 2 clients)
and observing such info in dmesg on the client side. could you put some light on this dmesg entry?
is it a bug or misconfiguration? i can provide more information about nfs configuration
if necessary but denying caching doesn't look nicely.

i'm using following nfs related packages:

autofs-5.0.5-1.x86_64
libnfsidmap-0.25-4.x86_64
nfs-utils-1.2.7-1.x86_64
nfs-utils-clients-1.2.7-1.x86_64
nfs-utils-common-1.2.7-1.x86_64

BR,
Paweł.

please CC me on reply.


             reply	other threads:[~2012-12-19 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 18:58 Paweł Sikora [this message]
2012-12-19 19:30 ` [3.6.11] NFS: Cache request denied due to non-unique superblock keys Jim Rees
2012-12-19 19:35 ` Myklebust, Trond
2012-12-19 21:16   ` Paweł Sikora
2012-12-19 22:06     ` Myklebust, Trond
2012-12-20 13:42       ` David Howells

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=6078496.RFsWrNWv86@localhost \
    --to=pawel.sikora@agmk.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox