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: 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: 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
