Comaring nfs on two nfs clients

[Ed Greshko]

On 05/13/13 18:01, Frank Murphy wrote:
> Client one:
> ~$ lsmod | grep nfs
> nfsv4                 242721  0 
> nfs                   169344  1 nfsv4
> dns_resolver           13096  1 nfs
> fscache                60427  2 nfs,nfsv4
> nfsd                  283278  13 
> auth_rpcgss            48560  2 nfsd,nfsv4
> nfs_acl                12741  1 nfsd
> lockd                  93540  2 nfs,nfsd
> sunrpc                256729  41
> nfs,nfsd,auth_rpcgss,lockd,nfsv4,nfs_acl
>
> Client two:
> ~$ lsmod | grep nfs
> nfsd                  283278  13 
> auth_rpcgss            48560  1 nfsd
> nfs_acl                12741  1 nfsd
> lockd                  93540  1 nfsd
> sunrpc                256729  21 nfsd,auth_rpcgss,lockd,nfs_acl
>
>
> Client one, connects to yum-server with autosfs,
> Client two does, not
>
> Same version kernel, selinux*, auto.* files
> on both boxes.
>
> The difference seems to be loaded mods.
> The server is also F18.
>

Client two appears to be running the nfs-server.service, nfsd is running.  It doesn't have any nfs file-systems mounted.  The modules won't get loaded until that happens.

Are you saying that Client two has autofs configured the same way as Client one?  Did you remember to enable/start the autofs.service?

systemctl status autofs.service


-- 
The only thing worse than a poorly asked question is a cryptic answer.