AnsweredAssumed Answered

/mapr could not be mounted automatically after reboot while manual mount works

Question asked by jqin Employee on Jun 20, 2017
Latest reply on Jun 23, 2017 by jqin

Hi, 

 

I have a cluster with MapR 5.2.1 and MEP 3.0.0 on cents 7.3, setup manually. While everything seems to be working fine, and I can also mount the cluster FS manually to /mapr, the automatic mount after reboot does not work as expected. 

 

I followed this doc to setup the automatic mount: Mounting NFS to MapR-FS on a Cluster Node. Here is what I have in /opt/mapr/conf/mapr_fstab:

localhost:/mapr /mapr hard,nolock

 

One thing I noticed is when I perform manually mount,  while the mounting worked, there are many lines of errors in /opt/mapr/logs/nfsserver.log like:

 

2017-06-20 09:29:24,3504 WARN nfsserver[5875] fs/nfsd/nfsserver.cc:564 127.0.0.1[0xe19fb4b4] NFS: unsupported NFS version:4, prog=0, bufLen=40
2017-06-20 09:29:24,3540 ERROR nfsserver[5875] fs/nfsd/mount.cc:2421 0.0.0.0[0] recvfrom returned err(Resource temporarily unavailable) -1

2017-06-20 09:29:24,3540 ERROR nfsserver[5875] fs/nfsd/mount.cc:2421 0.0.0.0[0] recvfrom returned err(Resource temporarily unavailable) -1

...

 

The ERROR line repeated many times. The WARN line is disappeared when I perform the manual mount with 

   -o nfsvers=3,hard,nolock

 

Not sure whether these lines matter ...

 

In addition,

  • License is NOT an issue here, I have a trial one.
  • I have mapr-nfs installed everywhere, nfs service is started everywhere as well
  • rpcbind is running 
  • /opt/mapr/conf/daemon.conf has:

[root@jqin-co73-88 ~]# cat /opt/mapr/conf/daemon.conf
mapr.daemon.user=mapr
mapr.daemon.group=mapr
mapr.uninstall.delete.group=1
mapr.uninstall.delete.user=1
mapr.daemon.runuser.warden=1

which are all seem to be fine.

 

Any clue why automatic mount is not working ?  Thanks

Outcomes