From: Jeff Garzik <jeff@garzik.org>
To: Andy Adamson <androsadamson@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [NFS v4.1] State manager error 22?
Date: Tue, 28 Aug 2012 13:09:14 -0400 [thread overview]
Message-ID: <CAFtxgO7qM+FDMEMUOVe1Z+LcYHmtQAPUdxd1zeGqtpidFo1wfQ@mail.gmail.com> (raw)
In-Reply-To: <CAHVgHyXBu5Ocb+MiAjbL_tn3CVx19+usbnDr1R-n4S9PCjK78A@mail.gmail.com>
On Tue, Aug 28, 2012 at 12:31 PM, Andy Adamson <androsadamson@gmail.com> wrote:
> nfs4_verify_fore_channel_attrs and nfs4_verify_back_channel_attrs was
> what I was looking at. I would also check the server responses (and
> the client reaction!) against rfc5661.
>
> Have you turned on client debugging to /var/log/messages? This turns
> it all on which for a mount failure is ok.
>
> # rpcdebug -v -m nfs -s all
Will give that a try. But it looks like I need to rebuild with
CONFIG_NFS_DEBUG...
Jeff
prev parent reply other threads:[~2012-08-28 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 15:39 [NFS v4.1] State manager error 22? Jeff Garzik
2012-08-28 16:06 ` Andy Adamson
2012-08-28 16:11 ` Jeff Garzik
2012-08-28 16:31 ` Andy Adamson
2012-08-28 17:09 ` Jeff Garzik [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=CAFtxgO7qM+FDMEMUOVe1Z+LcYHmtQAPUdxd1zeGqtpidFo1wfQ@mail.gmail.com \
--to=jeff@garzik.org \
--cc=androsadamson@gmail.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 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).