All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Weston Andros Adamson <dros@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Failure to mount nfsv4 on 3.12.0-rc5-wl+
Date: Tue, 22 Oct 2013 10:25:42 -0700	[thread overview]
Message-ID: <5266B516.4080507@candelatech.com> (raw)
In-Reply-To: <8F3401DF-10CB-43BB-956B-76D166C4B3EA@netapp.com>

On 10/22/2013 10:18 AM, Weston Andros Adamson wrote:
> 
> On Oct 22, 2013, at 1:09 PM, Ben Greear <greearb@candelatech.com> wrote:
> 
>> This is on an un-hacked upstream kernel (ath tree).  Mounting an older
>> Fedora 13 system with nfsv3 works fine, but mounting a F17 box with
>> NFSv4 hangs.  Ctrl-c of the process yields this error:
>>
>> NFS: nfs4_discover_server_trunking unhandled error -512. Exiting with error EIO
> 
> I have seen this error message and I'm currently debugging it - it's due to a hang in GSSD upcall.  This message is generated when the user ^Cs the mount. This is reproducible, but the hang only happens for me every once in a while. I can make it happen pretty reliably if I call mount/unmount a bunch of times (like the test_sec_options.sh script I posted last week).
> 
> This issue is next on my list...

Ok, no problem.  The vers=3 thing is fine for me.

I do seem to have a good system for reproducing the problem if you
create some patches for testing...

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      parent reply	other threads:[~2013-10-22 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 17:09 Failure to mount nfsv4 on 3.12.0-rc5-wl+ Ben Greear
2013-10-22 17:18 ` Weston Andros Adamson
2013-10-22 17:21   ` Weston Andros Adamson
2013-10-22 17:27     ` Ben Greear
2013-10-22 17:42       ` Weston Andros Adamson
2013-10-22 17:25   ` Ben Greear [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=5266B516.4080507@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=dros@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.