Stopping/Starting a Gluster volume resets ownership
Issue
- We have noticed that if you stop and start a Gluster volume the ownership of the mount reverts to root/root. For example, On a client machine with the volume mounted as "testvol" we see:
drwxr-xr-x 30 testuser testuser 4096 Dec 2 10:18 testvol
- We then stop and start the volume on the storage server:
[root@rhs-xxx xxxx]# gluster volume stop testvol
Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y
volume stop: testvol: success
[root@rhs-xxx xxxx]# gluster volume start testvol
volume start: testvol: success
- Immediately after we look at the mount point again and see:
drwxr-xr-x 30 root root 4096 Dec 2 10:18 testvol
Environment
- Red Hat Storage Server 2.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
