Hi, I have a CES node exporting some filesystems vis smb and ganesha in a standard CES setup. Now I want to mount a nfs share from a different, non-CES server on this CES node. This did not work: mount -o -fstype=nfs4,minorversion=1,rw,rsize=65536,wsize=65536 some.other.server:/some/path /mnt/ mount.nfs: mount to NFS server 'some.other.server:/some/path' failed: RPC Error: Program unavailable
Does the CES software stack interfere with the nfs client setup? It seems that at least with rpc-statd there is some conflict: systemctl status rpc-statd ● rpc-statd.service - NFS status monitor for NFSv2/3 locking. Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2020-10-21 17:48:21 CEST; 22min ago Process: 19896 ExecStart=/usr/sbin/rpc.statd $STATDARGS (code=exited, status=1/FAILURE) Oct 21 17:48:21 mynode systemd[1]: Starting NFS status monitor for NFSv2/3 locking.... Oct 21 17:48:21 mynode rpc.statd[19896]: Statd service already running! Oct 21 17:48:21 mynode systemd[1]: rpc-statd.service: control process exited, code=exited status=1 Oct 21 17:48:21 mynode systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. Oct 21 17:48:21 mynode systemd[1]: Unit rpc-statd.service entered failed state. Oct 21 17:48:21 mynode systemd[1]: rpc-statd.service failed. -- Dr. Jürgen Hannappel DESY/IT Tel. : +49 40 8998-4616 _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
