# Ansible facts missing nfs mounts

**URL:** <https://forum.ansible.com/t/ansible-facts-missing-nfs-mounts/16407>\
**Category:** Ansible Project\
**Created:** [October 2, 2014, 3:57pm UTC](https://forum.ansible.com/t/ansible-facts-missing-nfs-mounts/16407 "2014-10-02T15:57:17Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mzp45](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@Mzp45](https://forum.ansible.com/u/Mzp45)\
**Post date:** [October 2, 2014, 3:57pm UTC](https://forum.ansible.com/t/ansible-facts-missing-nfs-mounts/16407/1 "2014-10-02T15:57:17Z")

</div>

Hi,  
The facts that are returned from a machine are missing the hard mounted nfs mounts. So something like this in fstab is not available as a fact

:/vol/vol1/ / nfs bg,ro,hard,intr,tcp 0 0

Looking at the facts collection script, it looks like only local devices are being collected (at least on Linux). Is there a reason why the nfs mounts are not included? and is there an alternative way to collect them?

Thanks

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [October 2, 2014, 4:06pm UTC](https://forum.ansible.com/t/ansible-facts-missing-nfs-mounts/16407/2 "2014-10-02T16:06:34Z")

</div>

I was the one that added the original code for this, i left out all virtual and network systems for simplicity, there should be no problem adding networked filesystems and mount, I should just do it under a different key to avoid changing the current expectations.

Brian Coca

---

<div class="post-metadata">

**Author:** ![Mzp45](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@Mzp45](https://forum.ansible.com/u/Mzp45)\
**Post date:** [October 2, 2014, 4:18pm UTC](https://forum.ansible.com/t/ansible-facts-missing-nfs-mounts/16407/3 "2014-10-02T16:18:46Z")

</div>

Thanks - would that be available in the next release?

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [October 2, 2014, 8:56pm UTC](https://forum.ansible.com/t/ansible-facts-missing-nfs-mounts/16407/4 "2014-10-02T20:56:20Z")

</div>

I can’t commit to whether that would or wouldn’t be included.

---

<div class="post-metadata">

**Author:** ![Mzp45](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@Mzp45](https://forum.ansible.com/u/Mzp45)\
**Post date:** [October 3, 2014, 12:59pm UTC](https://forum.ansible.com/t/ansible-facts-missing-nfs-mounts/16407/5 "2014-10-03T12:59:23Z")

</div>

Ok. Do you mean just for the next release or for future?  
Would you guys be interested in a pull request if we wrote a module for this?

Thanks

---

<div class="post-metadata">

**Author:** ![Eric\_Wedaa](https://avatars.discourse-cdn.com/v4/letter/e/c0e974/32.png) [@Eric\_Wedaa](https://forum.ansible.com/u/Eric_Wedaa)\
**Post date:** [October 5, 2014, 5:51pm UTC](https://forum.ansible.com/t/ansible-facts-missing-nfs-mounts/16407/6 "2014-10-05T17:51:13Z")

</div>

This would be handy for me as well, as we have to mount AIX Repos to our AIX servers, and sometimes they are not always mounted. Being able to mount them when they are missing would be a good thing. (Otherwise I have to just mount it, and take the error, or do some kind of test for a file inside the repo and hope the file is always there.