Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:62740 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753914Ab3BMA2z (ORCPT ); Tue, 12 Feb 2013 19:28:55 -0500 Message-ID: <511ADE41.2040904@RedHat.com> Date: Tue, 12 Feb 2013 19:28:49 -0500 From: Steve Dickson MIME-Version: 1.0 To: "J. Bruce Fields" CC: Trond Myklebust , "J. Bruce Fields" , "David P. Quigley" , Linux NFS list , Linux FS devel list , Linux Security List , SELinux List Subject: Re: [PATCH 00/15] lnfs: 3.8-rc6 release References: <1360327163-20360-1-git-send-email-SteveD@redhat.com> <20130213001141.GA14195@fieldses.org> <20130213002117.GB14195@fieldses.org> In-Reply-To: <20130213002117.GB14195@fieldses.org> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-nfs-owner@vger.kernel.org List-ID: On 12/02/13 19:21, J. Bruce Fields wrote: > On Tue, Feb 12, 2013 at 07:11:41PM -0500, J. Bruce Fields wrote: >> I get failures on NFSv4 mounts after applying these patches. >> >> # mount -tnfs4 pip1:/exports/ext4 /mnt/ >> mount.nfs4: mounting pip1:/exports/ext4 failed, reason given by server: No such file or directory >> >> In wireshark I don't see an error, but I do notice that the final >> rpc request and reply is a getattr with bitmap 0, which is odd. > > Oh, and that was a build with labeled nfs configured out. Drop the -tnfs4 option... I think it has something to do with breaking up the version into modules... I never investigated why that worked... steved.