@Deaks @HGeorge    This issue can occur if you had some previous mount points and later if you have unmounted them. In some unusual scenarios, CM agent will still tries to grab the filesystem information of that mount point and fails.   To temporarily suppress this error, update the /etc/cloudera-scm-agent/config.ini on each of the hosts affected to: 1. In the line that lists the nodev filesystems: # The list of non-device (nodev) filesystem types which will be monitored. monitored_nodev_filesystem_types=nfs,nfs4,tmpfs   2. Please change the uncommented line to read as : monitored_nodev_filesystem_types=nfs,nfs4   3. Restart the cloudera manager agent with: service cloudera-scm-agent restart   Br, Tarun Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   ... View more