# Unable to register NFS for snapshot

**URL:** <https://discuss.elastic.co/t/unable-to-register-nfs-for-snapshot/186026>\
**Category:** Elasticsearch\
**Created:** [June 17, 2019, 9:16am UTC](https://discuss.elastic.co/t/unable-to-register-nfs-for-snapshot/186026 "2019-06-17T09:16:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [June 17, 2019, 9:21am UTC](https://discuss.elastic.co/t/unable-to-register-nfs-for-snapshot/186026/2 "2019-06-17T09:21:48Z")

</div>

NFS permission issues are often because the Elasticsearch process is not running as the same numerical UID or GID on each node, without compensating for this in the NFS configuration, meaning that when one node creates a subdirectory of the repository it is not possible for the other nodes to modify it. That is the first thing I would check.

> [@Error when creating a Snapshot Repository](https://discuss.elastic.co/t/error-when-creating-a-snapshot-repository/152587/2):
>
> It's better to share the whole stack trace of the exception and the whole error message - even though they can be quite long, they also include useful information. I'm going to guess that the Elasticsearch process is not running as the same numerical UID or GID on each node, and your NFS configuration does not compensate for this, meaning that when one node creates a subdirectory of the repository it is not possible for the other nodes to modify it.

---

_[View the full topic](https://discuss.elastic.co/t/unable-to-register-nfs-for-snapshot/186026)._