From: Bryan Schumaker <bjschuma@netapp.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Subject: Re: kernel BUG at /data/lemmy/linux.trees.git/fs/nfs/idmap.c:681!
Date: Fri, 28 Sep 2012 09:21:26 -0400 [thread overview]
Message-ID: <5065A456.4070007@netapp.com> (raw)
In-Reply-To: <20120928121733.GD18962@8bytes.org>
On 09/28/2012 08:17 AM, Joerg Roedel wrote:
> On Thu, Sep 27, 2012 at 02:15:21PM -0400, Bryan Schumaker wrote:
>
>> Double check that you're using the legacy idmapper, and not the
>> keyring based one (/etc/request-key.conf shouldn't have the "create
>> id_resolver * * /usr/bin/nfsidmap %k %d" line).
>
> That should only be relevant for NFSv4, no? I am using v3 only (without
> explicitly setting the version as mount option).
Any idmapper problem is only relevant to v4, so if you're seeing a problem that means you're not using NFS v3.
>
> Anyway, I had no luck on reproducing the failure again after
> re-installation of the box, either with of with-out my patches on-top. I
> tried a few different config settings for NFS too, but the BUG didn't
> trigger again :-/
Maybe it's mounting over v3 now? Can you retry using "vers=4" in your mount options?
- Bryan
>
>
> Joerg
>
>
next prev parent reply other threads:[~2012-09-28 13:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 13:41 kernel BUG at /data/lemmy/linux.trees.git/fs/nfs/idmap.c:681! Joerg Roedel
2012-08-07 13:55 ` Bryan Schumaker
2012-08-07 14:15 ` Joerg Roedel
2012-08-07 14:17 ` Bryan Schumaker
2012-08-07 14:27 ` Joerg Roedel
2012-08-07 14:36 ` Bryan Schumaker
2012-08-07 14:50 ` Joerg Roedel
2012-08-07 15:12 ` Bryan Schumaker
2012-08-07 15:19 ` Myklebust, Trond
2012-08-07 15:14 ` Myklebust, Trond
2012-08-07 15:18 ` Bryan Schumaker
2012-09-27 14:52 ` Joerg Roedel
2012-09-27 15:32 ` Myklebust, Trond
2012-09-27 15:39 ` Joerg Roedel
2012-09-27 16:16 ` Myklebust, Trond
2012-09-27 16:59 ` Linus Torvalds
2012-09-27 21:21 ` Myklebust, Trond
2012-09-27 17:56 ` Joerg Roedel
2012-09-27 18:15 ` Bryan Schumaker
2012-09-28 12:17 ` Joerg Roedel
2012-09-28 13:21 ` Bryan Schumaker [this message]
2012-09-28 13:34 ` Joerg Roedel
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=5065A456.4070007@netapp.com \
--to=bjschuma@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).