Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx12.netapp.com ([216.240.18.77]:28373 "EHLO mx12.netapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750811Ab3E3UlA convert rfc822-to-8bit (ORCPT ); Thu, 30 May 2013 16:41:00 -0400 From: "Myklebust, Trond" To: Chuck Lever CC: Jim Schutt , "Adamson, Dros" , Linux NFS Mailing List , LKML Kernel Subject: Re: 3.10-rc3 NFSv3 mount issues Date: Thu, 30 May 2013 20:40:58 +0000 Message-ID: <1369946457.3111.17.camel@leira.trondhjem.org> References: <51A7B442.9010108@sandia.gov> In-Reply-To: Content-Type: text/plain; charset=US-ASCII MIME-Version: 1.0 Sender: linux-nfs-owner@vger.kernel.org List-ID: On Thu, 2013-05-30 at 16:26 -0400, Chuck Lever wrote: > On May 30, 2013, at 4:19 PM, Jim Schutt wrote: > > > Hi, > > > > I've been trying to test 3.10-rc3 on some diskless clients, and found > > that I can no longer mount my root file system via NFSv3. > > > > I poked around looking at NFS changes for 3.10, and found these two > > commits: > > > > d497ab9751 "NFSv3: match sec= flavor against server list" > > 4580a92d44 "NFS: Use server-recommended security flavor by default (NFSv3)" > > > > If I revert both of these commits from 3.10-rc3, then my diskless > > client can mount its root file system. > > > > The busybox mount command fails like this, when using 3.10-rc3: > > > > / # mount -t nfs -o ro,nolock,vers=3,proto=tcp 172.17.0.122:/gmi/images/jaschut/ceph.toss-2x /mnt > > mount: mounting 172.17.0.122:/gmi/images/jaschut/ceph.toss-2x on /mnt failed: Invalid argument > > > > The commit messages for both these commits seem to say that mounting > > with the "sys=sec" option should work, but unfortunately, my busybox doesn't > > seem to understand the "sec=" mount option: > > > > / # mount -t nfs -o ro,nolock,vers=3,proto=tcp,sec=sys 172.17.0.122:/gmi/images/jaschut/ceph.toss-2x /mnt > > mount: invalid number 'sys' > > > > My NFS server is based on RHEL6, and is not using any "sec=" option > > in its export for this file system. I did try exporting with "sec=sys", > > but it didn't seem to make any difference either. > > > > So far, this seems like a regression to me .... > > Any ideas what I might be doing wrong? How can I > > help make this work again? > > 3.10-rc3 appears to be missing the fix for this. See: > > http://marc.info/?l=linux-nfs&m=136855668104598&w=2 > > Trond, can we get this applied? > For some reason it got lost in the mail heap. I've applied it now to the 'bugfixes' branch. Will push upstream in the next few days... -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@netapp.com www.netapp.com