From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.parallels.com ([64.131.90.16]:58056 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751243Ab0L3JYW (ORCPT ); Thu, 30 Dec 2010 04:24:22 -0500 Message-ID: <4D1C4C7C.6050606@parallels.com> Date: Thu, 30 Dec 2010 03:10:20 -0600 From: Rob Landley To: "Kirill A. Shutemov" CC: Rob Landley , Trond Myklebust , "J. Bruce Fields" , Neil Brown , Pavel Emelyanov , , "David S. Miller" , , Subject: Re: [PATCH v2 00/12] make rpc_pipefs be mountable multiple time References: <1293628470-28386-1-git-send-email-kas@openvz.org> <20101230085139.GA29697@shutemov.name> In-Reply-To: <20101230085139.GA29697@shutemov.name> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 On 12/30/2010 02:51 AM, Kirill A. Shutemov wrote: > On Wed, Dec 29, 2010 at 08:13:50PM -0600, Rob Landley wrote: >> On Wed, Dec 29, 2010 at 7:14 AM, Kirill A. Shutemov wrote: >>> >>> Prepare nfs/sunrpc stack to use multiple instances of rpc_pipefs. >>> Only for client for now. >> >> What would a test case for this look like? (Is there some way to tell >> an nfs mount to use a specific instance of rpc_pipefs or something?) > > You can create a new instance of rpc_pipefs using 'newinstance' > mountoption. > > Then you can specify which rpc_pipefs to use with 'rpcmount' mountoption > of nfs mount. If none specifed, '/var/lib/nfs/rpc_pipefs' uses by default. That path is as the process performing the mount sees it? > If no rpcmount mountoption, no rpc_pipefs was found at > '/var/lib/nfs/rpc_pipefs' and we are in init's mount namespace, we use > init_rpc_pipefs. It's the "we are in init's mount namespace" that I was wondering about. So if I naievely chroot, nfs mount stops working the way it did before I chrooted unless I do an extra setup step? I'm actually poking at getting nfs mount working in LXC containers with different network routing (mostly study so far, it took me a couple weeks just to get lxc to work for me and now I'm trying to wrap my head around Linux's NFS implementation), so I'm very interested in this... Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Landley Subject: Re: [PATCH v2 00/12] make rpc_pipefs be mountable multiple time Date: Thu, 30 Dec 2010 03:10:20 -0600 Message-ID: <4D1C4C7C.6050606@parallels.com> References: <1293628470-28386-1-git-send-email-kas@openvz.org> <20101230085139.GA29697@shutemov.name> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: Rob Landley , Trond Myklebust , "J. Bruce Fields" , Neil Brown , Pavel Emelyanov , , "David S. Miller" , , To: "Kirill A. Shutemov" Return-path: In-Reply-To: <20101230085139.GA29697-oKw7cIdHH8eLwutG50LtGA@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On 12/30/2010 02:51 AM, Kirill A. Shutemov wrote: > On Wed, Dec 29, 2010 at 08:13:50PM -0600, Rob Landley wrote: >> On Wed, Dec 29, 2010 at 7:14 AM, Kirill A. Shutemov wrote: >>> >>> Prepare nfs/sunrpc stack to use multiple instances of rpc_pipefs. >>> Only for client for now. >> >> What would a test case for this look like? (Is there some way to tell >> an nfs mount to use a specific instance of rpc_pipefs or something?) > > You can create a new instance of rpc_pipefs using 'newinstance' > mountoption. > > Then you can specify which rpc_pipefs to use with 'rpcmount' mountoption > of nfs mount. If none specifed, '/var/lib/nfs/rpc_pipefs' uses by default. That path is as the process performing the mount sees it? > If no rpcmount mountoption, no rpc_pipefs was found at > '/var/lib/nfs/rpc_pipefs' and we are in init's mount namespace, we use > init_rpc_pipefs. It's the "we are in init's mount namespace" that I was wondering about. So if I naievely chroot, nfs mount stops working the way it did before I chrooted unless I do an extra setup step? I'm actually poking at getting nfs mount working in LXC containers with different network routing (mostly study so far, it took me a couple weeks just to get lxc to work for me and now I'm trying to wrap my head around Linux's NFS implementation), so I'm very interested in this... Rob -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html