All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olga Kornievskaia <aglo@umich.edu>
To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
Cc: linux-nfs <linux-nfs@vger.kernel.org>, Andy Adamson <andros@netapp.com>
Subject: Re: "nfs4_discover_server_trunking unhandled error" on Ctrl-C
Date: Tue, 13 Jun 2017 12:21:01 -0400	[thread overview]
Message-ID: <CAN-5tyHeaNHVxQLnXVfQyyS20jwk0L-2UjY-pH-azM6ADQBEtQ@mail.gmail.com> (raw)
In-Reply-To: <991293071.14131572.1497360717136.JavaMail.zimbra@desy.de>

On Tue, Jun 13, 2017 at 9:31 AM, Mkrtchyan, Tigran
<tigran.mkrtchyan@desy.de> wrote:
>
> If I hit Ctrl-C during mount, then I see following message in the log file:
>
>  NFS: nfs4_discover_server_trunking unhandled error -512. Exiting with error EIO
>
>
> produced at nfs4state.c:2533. Is this expected behavior?

What kernel version (or upstream commit) is that? Is this
reproducible? Anything on the network trace that server returns that
could explain an error it doesn't expect. Also I'm thinking that
nfs_wait_client_init_complete() could be interrupted by ctrl-c and
return ERESTARTSYS and that could translate to "unhanded error".

  reply	other threads:[~2017-06-13 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 13:31 "nfs4_discover_server_trunking unhandled error" on Ctrl-C Mkrtchyan, Tigran
2017-06-13 16:21 ` Olga Kornievskaia [this message]
2017-06-13 19:22   ` Mkrtchyan, Tigran
2017-06-14 12:29     ` Jeff Layton
2017-06-14 14:09       ` Chuck Lever

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=CAN-5tyHeaNHVxQLnXVfQyyS20jwk0L-2UjY-pH-azM6ADQBEtQ@mail.gmail.com \
    --to=aglo@umich.edu \
    --cc=andros@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    /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.