[Gluster-users] GlusterFS permission problem

[Rajesh Amaravathi]

i see that for EASEGFS, you have used netopstorage<n> hostnames; 0 < n < 5. 
Are these hostnames resolvable under /etc/hosts on all hosts or local DNS? 
If yes, have you tried setting trusted write = off? 


What exactly is the problem when you say it doesnt work? 
what are the symptoms? please elucidate. 


Regards, 
Rajesh Amaravathi, 
Software Engineer, GlusterFS 
RedHat Inc. 
----- Original Message -----

From: "lihang" <lihang at netopcomputing.com> 
To: "Rajesh Amaravathi" <rajesh at redhat.com> 
Cc: "gluster-users" <gluster-users at gluster.org> 
Sent: Tuesday, June 12, 2012 9:43:55 AM 
Subject: Re: Re: [Gluster-users] GlusterFS permission problem 


HI 
Thank you for your help. The permission problem has been solved by changing the version to 3.3. 
But there is a new problem. I new two volumes. The volume TEST is everything ok. But when I mount the volume EASEGFS through the nfs .I could not see anything . 
They work ok under the glusterfs all. What can I do ? 


gluster> volume info 

Volume Name: TEST 
Type: Stripe 
Volume ID: 5505d928-9a60-4c80-aa22-61c2933868cd 
Status: Started 
Number of Bricks: 1 x 2 = 2 
Transport-type: tcp 
Bricks: 
Brick1: 10.194.60.216:/test1 
Brick2: 10.194.60.216:/test2 
Options Reconfigured: 
nfs.addr-namelookup: off 
network.ping-timeout: 5 
nfs.trusted-write: on 

Volume Name: EASEGFS 
Type: Stripe 
Volume ID: b2f94b9f-3254-40ba-8ac2-5f6de8d83958 
Status: Started 
Number of Bricks: 1 x 4 = 4 
Transport-type: tcp 
Bricks: 
Brick1: netopstorage1:/ease 
Brick2: netopstorage2:/ease 
Brick3: netopstorage3:/ease 
Brick4: netopstorage4:/ease 
Options Reconfigured: 
nfs.trusted-write: on 
network.ping-timeout: 5 
nfs.addr-namelookup: off 


lihang 



From: Rajesh Amaravathi 
Date: 2012-05-31 15:07 
To: lihang 
CC: gluster-users 
Subject: Re: [Gluster-users] GlusterFS permission problem 

In 3.2.5, NLM is not implemented for our NFS server. you can try mounting with nolock option, it should work. 
If you need locking, we have NLM implementation in the latest release 3.3. 

Regards, 
Rajesh Amaravathi, 
Software Engineer, GlusterFS 
RedHat Inc. 

----- Original Message ----- 
From: lihang at netopcomputing.com 
To: "Rajesh Amaravathi" <rajesh at redhat.com> 
Cc: gluster-users at gluster.org 
Sent: Thursday, 31 May, 2012 11:45:01 AM 
Subject: Re: [Gluster-users] GlusterFS permission problem 

HI 
The version I used is 3.2.5 .Thanks. 


lihang 

On Thu, 31 May 2012 02:09:09 -0400 (EDT), Rajesh Amaravathi wrote: 
> which version of glusterfs are you using? 
> 
> Regards, 
> Rajesh Amaravathi, 
> Software Engineer, GlusterFS 
> RedHat Inc. 
> 
> ----- Original Message ----- 
> From: lihang at netopcomputing.com 
> To: gluster-users at gluster.org 
> Sent: Thursday, 31 May, 2012 9:43:26 AM 
> Subject: [Gluster-users] GlusterFS permission problem 
> 
> HI,ALL 
> I found a strange problem. 
> I setup a GlusterFS between linux and windows by nfs and LDAP. 
> The windows client has mounted the volume successfully. But there are 
> some problem with permission . 
> I can new a file and edit it successfully on the volume at 
> windows.But 
> when I new a file in the application buy the "save as"button ,It 
> report 
> the error that I haven't the permission to edit it . 
> 
> My volume info: 
> Volume Name: share 
> Type: Distribute 
> Status: Started 
> Number of Bricks: 4 
> Transport-type: tcp 
> Bricks: 
> Brick1: 10.194.60.211:/data 
> Brick2: 10.194.60.212:/data 
> Brick3: 10.194.60.213:/data 
> Brick4: 10.194.60.214:/data 
> Options Reconfigured: 
> nfs.addr-namelookup: off 
> nfs.trusted-write: on 
> nfs.trusted-sync: on 
> features.quota: on 
> network.ping-timeout: 5 
> 
> windows mount commond : 
> mount 10.194.60.211:/share x: 
> 
> 
> -------------------------------------------------------------------------------- 
> 
> lihang 
> _______________________________________________ 
> Gluster-users mailing list 
> Gluster-users at gluster.org 
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120612/a210e666/attachment.html>