On Tue, Sep 6, 2016, 8:08 PM Pat Haley wrote:
>
> Trying the gluster client seems to fix the problem.
>
Hmm, suggests an NFS export issue then, rather than permissions issue?
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.cento
Trying the gluster client seems to fix the problem.
On 09/02/2016 12:57 AM, Chris Murphy wrote:
On Thu, Sep 1, 2016, 8:11 AM Pat Haley 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
On Thu, Sep 1, 2016, 8:11 AM Pat Haley 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:
>
> ---
For the enforcing=0, is that referring to SELinux? If so, we are not
running SELinux.
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
Try booting with enforcing=0 and if that fixes it, you need to find out
what security label is needed for gluster.
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.
If that's not it, maybe try the gluster clie
For example the directory /gdata/bibliography/Work/GroupBib/trunk/ can
be written in by user phaley but not by other users who are member of
the group mseasweb. The directory has permissions
[root@mseas ~]# ls -lh /gdata/bibliography/Work/GroupBib
total 12K
drwxrwsr-x 4 phaley mseasweb 4.0K
Stupid question, and note I missed most of the earlier posts in this
thread: what are the permissions on the directory that this directory are
in?
mark
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
So far, those look the same
client:
[root@mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/
getfacl: Removing leading '/' from absolute path names
# file: gdata/bibliography/Work/GroupBib/trunk/
# owner: phaley
# group: mseasweb
# flags: -s-
user::rwx
group::rwx
other::r-x
server
On 08/30/2016 03:01 PM, Pat Haley wrote:
the owner of a directory can still write to that directory but any
other member of the associated group cannot, even though the directory
clearly has group write permissions set
Use "getfacl" on both the client and server side to view the complete
per
Hi
We have just migrated our data to a new file server (more space, old
server was showing its age). We have a volume for collaborative use,
based on group membership. In our new server, the group write
permissions are not being respected (e.g. the owner of a directory can
still write to th
10 matches
Mail list logo