Return-Path: linux-nfs-owner@vger.kernel.org Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:39624 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751110Ab2H1RJQ (ORCPT ); Tue, 28 Aug 2012 13:09:16 -0400 Received: by lagy9 with SMTP id y9so3444240lag.19 for ; Tue, 28 Aug 2012 10:09:15 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 28 Aug 2012 13:09:14 -0400 Message-ID: Subject: Re: [NFS v4.1] State manager error 22? From: Jeff Garzik To: Andy Adamson Cc: linux-nfs@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, Aug 28, 2012 at 12:31 PM, Andy Adamson 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