On Thu, Sep 1, 2016, 8:11 AM Pat Haley phaley@mit.edu wrote:
For the enforcing=0, is that referring to SELinux? If so, we are not running SELinux.
OK so neither that nor chcon nor context mount option apply. It's something else.
On 08/31/2016 11:38 PM, Chris Murphy wrote:
Try booting with enforcing=0 and if that fixes it, you need to find out what security label is needed for gluster.
For the enforcing=0, is that referring to SELinux? If so, we are not running SELinux.
Chances are it's easiest to use -o context= mount option on the brick,
but
if the brick is not exclusive to gluster you'll need chcon -R.
We aren't sure exactly what you mean by this second paragraph, can you expand on this? Are these two exclusive options exclusive? We aren't sure what you what you mean by "exclusive to gluster"
If that's not it, maybe try the gluster client instead of using NFS. See
if
you get a different result that narrows down what's going on.
My vague recollection is for Samba, without the correct SELinux label, I could neither read nor write.
Chris Murphy _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley@mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
-
Chris Murphy