# Cant seem to mount volume with neo4j 3.3.9 (path in use?)

**URL:** <https://community.neo4j.com/t/cant-seem-to-mount-volume-with-neo4j-3-3-9-path-in-use/9889>\
**Category:** Aura & Cloud\
**Tags:** kubernetes\
**Created:** [September 5, 2019, 8:36am UTC](https://community.neo4j.com/t/cant-seem-to-mount-volume-with-neo4j-3-3-9-path-in-use/9889 "2019-09-05T08:36:15Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![njmmeibergen](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/njmmeibergen/32/4837_2.png) [@njmmeibergen](https://community.neo4j.com/u/njmmeibergen)\
**Post date:** [September 9, 2019, 6:57am UTC](https://community.neo4j.com/t/cant-seem-to-mount-volume-with-neo4j-3-3-9-path-in-use/9889/5 "2019-09-09T06:57:14Z")

</div>

Hi David,

Indeed, it was an issue of rights of writing data to Azure. In particular in the setup of the `StorageClass` in Kubernetes, you can set additional `mountOptions`. One of those is the `uid` which should be set to 100 - the user id used for neo4j.

Example of the StorageClass yaml:

```
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: azurefile-neo4j
provisioner: kubernetes.io/azure-file
reclaimPolicy: Retain
mountOptions:
  - dir_mode=0755
  - file_mode=0755
  - uid=100 # Allow write access for neo4j
  - gid=1000
parameters:
  skuName: Standard_LRS

```

It is curious though that the file `/data/dbms` was written successful before, while `/data/databases` could not be written. Seems that dbms and databases are created by different users? But that would be a separate question.

---

_[View the full topic](https://community.neo4j.com/t/cant-seem-to-mount-volume-with-neo4j-3-3-9-path-in-use/9889)._