From: Nick Bowler <nbowler@elliptictech.com>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at fs/nfs/idmap.c:684!
Date: Mon, 17 Sep 2012 10:04:05 -0400 [thread overview]
Message-ID: <20120917140405.GA19032@elliptictech.com> (raw)
In-Reply-To: <50571F51.9080100@netapp.com>
Hello Bryan,
On 2012-09-17 09:02 -0400, Bryan Schumaker wrote:
> Two questions:
> 1) How sure are you that you're using v3? Make sure you're using the
> 'vers=3' mount option. I'm not sure which version of nfs-utils Debian
> uses, but recent versions set v4 as the default.
I looked in /proc/mounts and all of them had vers=3. But...
> 2) Can you try Linux 3.5.4? Patches for the idmapper issue have
> already been accepted.
...indeed, Linux 3.5.4 seems to be working. Moreover, if I look at
/proc/mounts now I do in fact see a single line with vers=4. I guess
the v4 mount is what crashed so it didn't show up in the list.
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
prev parent reply other threads:[~2012-09-17 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 19:20 PROBLEM: kernel BUG at fs/nfs/idmap.c:684! Nick Bowler
2012-09-17 13:02 ` Bryan Schumaker
2012-09-17 14:04 ` Nick Bowler [this message]
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=20120917140405.GA19032@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=bjschuma@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).