discrepancies in mount output

[J. Bruce Fields]

On Thu, Jun 26, 2008 at 03:32:35PM +0200, Guillaume Rousse wrote:
> Guillaume Rousse a écrit :
> > On first host, I have:
> > rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> > 
> > On second host, I have:
> > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> > 
> > Both are nfs4 clients. Is this normal ?

Yes.

> And before someone ask:
> - they are both x86 hosts
> - they have the same mount version (util-linux-ng-2.13.1)
> - they run approximatively same kernel (2.6.24.5 + a few nfs patches for 
>   the one displaying rpc_pipefs insteaf of sunrpc).
> 
> find /var/lib/nfs/rpc_pipefs return the same content, so it seems to be 
> only cosmetic:
> /var/lib/nfs/rpc_pipefs
> /var/lib/nfs/rpc_pipefs/statd
> /var/lib/nfs/rpc_pipefs/portmap
> /var/lib/nfs/rpc_pipefs/nfs
> /var/lib/nfs/rpc_pipefs/mount
> /var/lib/nfs/rpc_pipefs/lockd

The rpc_pipefs filesystem is used by rpc.gssd and rpc.idmapd to
communicate with the kernel nfs client.  It needs to be mounted on the
client if you want rpcsec_gss or NFSv4 to work.

It also doesn't hurt to keep it mounted on the server (and the server
will use it in the future for rpcsec_gss callbacks).

--b.