Re: [Gluster-users] Cannot rename files with root squashing and r-x folder group permissions

2014-07-14 Thread Raghavendra Bhat 

On Monday 14 July 2014 09:10 PM, Pranith Kumar Karampuri wrote:

CCed Raghavendra Bhat who may know about the issue

Pranith
On 07/14/2014 08:01 PM, Joe Julian wrote:

https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS

Please file a bug report.

On July 14, 2014 12:38:11 AM PDT, David Raffelt 
 wrote:


Hi All,
After a recent update to gluster 3.5 we are having some issues
renaming files when root squashing is enabled and the folder
group permissions are not set to write.

For example if I create a folder with the following permissions
$ mkdir test
$ chmod g-w test
$ ls -l
drwxr-xr-x  2 dave dave  22 Jul 14 17:16 test

When I create a file /within/ this folder, and try to rename it I
get a file permissions error.

$ cd test
$ touch asdf
$ mv asdf asdf2
mv: cannot move 'asdf' to 'asdf2': Permission denied

A strace on the mv command reveals the rename system call fails with:
rename("asdf", "asdf2") = -1 EACCES (Permission denied)

However I can copy the file and delete the old one fine.

If I either disable gluster root squashing, or change the
test_dir folder group permission to write then I can rename the
file without any problems.

System details are:
Arch linux
System umask is set to 002
Distributed volume, 3 peers, 1 brick per peer.

Any help is much appreciated!
Dave




Hi Dave,

Can you please provide the brick and client log files? Which client you 
were using? fuse or nfs?


Regards,
Raghavendra Bhat




Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users




___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Gluster vs NFS export sync

2014-07-14 Thread Franco Broi 

I think the option I need is noac.

On Fri, 2014-07-11 at 16:10 +0530, Santosh Pradhan wrote: 
> On 07/11/2014 02:37 PM, Franco Broi wrote:
> > On Fri, 2014-07-11 at 14:22 +0530, Santosh Pradhan wrote:
> >> On 07/11/2014 06:10 AM, Franco Broi wrote:
> >>> Hi
> >>>
> >>> Is there any way to make Gluster emulate the behaviour of a NFS
> >>> filesystem exported with the sync option? By that I mean is it possible
> >>> to write a file from one client and guarantee that the data will be
> >>> instantly available on close to all other clients?
> >> I think FUSE also supports the sync option with mount similar to NFS.
> > There's 2 types of NFS sync, server and client but they behave very
> > differently. With sync at the client end, NFS just calls fsync on close
> > (I think),
> 
> No. If the NFS client is mounted with sync flag i.e. -o sync, then all 
> the WRITEs will be synchronous i.e. they wont be cached in client side 
> and they(WRITEs) will hit the server with FILE_SYNC (stable write) flag 
> which is nothing but FILE I/O with O_SYNC flag.
> 
> > with sync at the server end, all writes are synchronous.
> >
> > Opening the file with O_SYNC also doesn't give the desired effect
> > although you'd think it would.
> It should be same as above.
> 
> Thanks,
> Santosh
> >   NFS must have some way of communicating
> > the file attribute changes to all the clients immediately the write
> > completes.
> >
> >> Man page snippet for fuse(8):
> >> OPTIONS
> >>  Most of the generic mount options described in mount are
> >> supported (ro, rw, suid, nosuid, dev,
> >>  nodev, exec, noexec, atime, noatime, sync, async, dirsync).
> >> Filesystems are mounted  with
> >>  nodev,nosuid by default, which can only be overridden by a
> >> privileged user.
> >>
> >> Thanks,
> >> Santosh
> >>
> >>> Cheers,
> >>>
> >>> ___
> >>> Gluster-users mailing list
> >>> Gluster-users@gluster.org
> >>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
> >
> 


___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Cannot rename files with root squashing and r-x folder group permissions

2014-07-14 Thread Pranith Kumar Karampuri 

CCed Raghavendra Bhat who may know about the issue

Pranith
On 07/14/2014 08:01 PM, Joe Julian wrote:

https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS

Please file a bug report.

On July 14, 2014 12:38:11 AM PDT, David Raffelt 
 wrote:


Hi All,
After a recent update to gluster 3.5 we are having some issues
renaming files when root squashing is enabled and the folder group
permissions are not set to write.

For example if I create a folder with the following permissions
$ mkdir test
$ chmod g-w test
$ ls -l
drwxr-xr-x  2 dave dave  22 Jul 14 17:16 test

When I create a file /within/ this folder, and try to rename it I
get a file permissions error.

$ cd test
$ touch asdf
$ mv asdf asdf2
mv: cannot move 'asdf' to 'asdf2': Permission denied

A strace on the mv command reveals the rename system call fails with:
rename("asdf", "asdf2") = -1 EACCES (Permission denied)

However I can copy the file and delete the old one fine.

If I either disable gluster root squashing, or change the test_dir
folder group permission to write then I can rename the file
without any problems.

System details are:
Arch linux
System umask is set to 002
Distributed volume, 3 peers, 1 brick per peer.

Any help is much appreciated!
Dave




Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Remove Replica Pair issue.

2014-07-14 Thread Robert Moss 
Thank you sac,

That worked like a champ. I also ran the same command on brick 2 of the pair.

Hopefully I will be able to help out in the future. Thank you again.

Best regards,

Rob Moss


From: Sachidananda Urs [mailto:s...@redhat.com]
Sent: Monday, July 14, 2014 9:44 AM
To: Robert Moss; gluster-users@gluster.org
Subject: Re: [Gluster-users] Remove Replica Pair issue.

Hey Rob,

On 07/14/2014 07:59 PM, Robert Moss wrote:

Gluster Gurus,

I am having an issue removing a gluster replica pair. I have tried numerous 
different iterations of the command and get back 'Incorrect brick 
tx4-gluster1-10:/brick10 for volume gv0'
Here is the output of "gluster volume info":

Volume Name: gv0
Type: Distributed-Replicate
Volume ID: 176c0a15-c107-4bdc-9b00-df7e5c841374
Status: Started
Number of Bricks: 10 x 2 = 20
Transport-type: tcp
Bricks:
Brick1: tx4-gluster1-1:/brick1/brick
Brick2: tx4-gluster1-2:/brick1/brick
Brick3: tx4-gluster1-3:/brick1/brick
Brick4: tx4-gluster1-4:/brick1/brick
Brick5: tx4-gluster1-5:/brick1/brick
Brick6: tx4-gluster1-6:/brick1/brick
Brick7: tx4-gluster1-7:/brick1/brick
Brick8: tx4-gluster1-8:/brick1/brick
Brick9: tx4-gluster1-9:/brick1/brick
Brick10: tx4-gluster1-10:/brick1/brick
Brick11: tx4-gluster1-1:/brick2/brick
Brick12: tx4-gluster1-2:/brick2/brick
Brick13: tx4-gluster1-3:/brick2/brick
Brick14: tx4-gluster1-4:/brick2/brick
Brick15: tx4-gluster1-5:/brick2/brick
Brick16: tx4-gluster1-6:/brick2/brick
Brick17: tx4-gluster1-7:/brick2/brick
Brick18: tx4-gluster1-8:/brick2/brick
Brick19: tx4-gluster1-9:/brick2/brick
Brick20: tx4-gluster1-10:/brick2/brick
Options Reconfigured:
nfs.disable: off

I would like to remove gluster1-10 from the gluster cluster.
Here is my command:

gluster volume remove-brick gv0 replica 2 tx4-gluster1-10:/brick1 
tx4-gluster1-10:/brick2 force

You are getting the command wrong here. You can remove the replica pairs, in 
your case the pairs are:

Brick9: tx4-gluster1-9:/brick1/brick
Brick10: tx4-gluster1-10:/brick1/brick

And your command would be:

gluster volume remove-brick gv0 replica 2 tx4-gluster1-9:/brick1/brick 
tx4-gluster1-10:/brick1/brick

And if I understand correctly you want to remove the host gluster1-10 from the 
cluster which is part of two replica pairs. So you will end up removing two 
replica pairs if you want to remove gluster1-10 from the cluster.

-sac



Here is the result:
volume remove-brick commit force: failed: Incorrect brick 
tx4-gluster1-10:/brick1 for volume gv0

I have tried a number of iterations here, using different names and trying 
tx4-gluster1-10 and 1-9 bricks. Nothing has worked so far.
This is a test setup so we don't care about data, we just need to learn.
We will probably not put the node back in after removal.
Any help would be greatly appreciated.
Thank you in advance.

Best regards,

Rob Moss





___

Gluster-users mailing list

Gluster-users@gluster.org

http://supercolony.gluster.org/mailman/listinfo/gluster-users

___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Remove Replica Pair issue.

2014-07-14 Thread Sachidananda Urs 

Hey Rob,

On 07/14/2014 07:59 PM, Robert Moss wrote:


/Gluster Gurus,/

//

/I am having an issue removing a gluster replica pair. I have tried 
numerous different iterations of the command and get back 'Incorrect 
brick tx4-gluster1-10:/brick10 for volume gv0'/


/Here is the output of "gluster volume info":/

Volume Name: gv0

Type: Distributed-Replicate

Volume ID: 176c0a15-c107-4bdc-9b00-df7e5c841374

Status: Started

Number of Bricks: 10 x 2 = 20

Transport-type: tcp

Bricks:

Brick1: tx4-gluster1-1:/brick1/brick

Brick2: tx4-gluster1-2:/brick1/brick

Brick3: tx4-gluster1-3:/brick1/brick

Brick4: tx4-gluster1-4:/brick1/brick

Brick5: tx4-gluster1-5:/brick1/brick

Brick6: tx4-gluster1-6:/brick1/brick

Brick7: tx4-gluster1-7:/brick1/brick

Brick8: tx4-gluster1-8:/brick1/brick

Brick9: tx4-gluster1-9:/brick1/brick

Brick10: tx4-gluster1-10:/brick1/brick

Brick11: tx4-gluster1-1:/brick2/brick

Brick12: tx4-gluster1-2:/brick2/brick

Brick13: tx4-gluster1-3:/brick2/brick

Brick14: tx4-gluster1-4:/brick2/brick

Brick15: tx4-gluster1-5:/brick2/brick

Brick16: tx4-gluster1-6:/brick2/brick

Brick17: tx4-gluster1-7:/brick2/brick

Brick18: tx4-gluster1-8:/brick2/brick

Brick19: tx4-gluster1-9:/brick2/brick

Brick20: tx4-gluster1-10:/brick2/brick

Options Reconfigured:

nfs.disable: off

/I would like to remove gluster1-10 from the gluster cluster./

/Here is my command:/

gluster volume remove-brick gv0 replica 2 tx4-gluster1-10:/brick1 
tx4-gluster1-10:/brick2 force




You are getting the command wrong here. You can remove the replica 
pairs, in your case the pairs are:



Brick9: tx4-gluster1-9:/brick1/brick

Brick10: tx4-gluster1-10:/brick1/brick

And your command would be:

gluster volume remove-brick gv0 replica 2 tx4-gluster1-9:/brick1/brick 
tx4-gluster1-10:/brick1/brick


And if I understand correctly you want to remove the host gluster1-10 
from the cluster which is part of two replica pairs. So you will end up 
removing two replica pairs if you want to remove gluster1-10 from the 
cluster.


-sac


/Here is the result:/

volume remove-brick commit force: failed: Incorrect brick 
tx4-gluster1-10:/brick1 for volume gv0


I have tried a number of iterations here, using different names and 
trying tx4-gluster1-10 and 1-9 bricks. Nothing has worked so far.


This is a test setup so we don't care about data, we just need to learn.

We will probably not put the node back in after removal.

Any help would be greatly appreciated.

Thank you in advance.

Best regards,

Rob Moss



___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Cannot rename files with root squashing and r-x folder group permissions

2014-07-14 Thread Joe Julian 
https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS

Please file a bug report.

On July 14, 2014 12:38:11 AM PDT, David Raffelt  wrote:
>Hi All,
>After a recent update to gluster 3.5 we are having some issues renaming
>files when root squashing is enabled and the folder group permissions
>are
>not set to write.
>
>For example if I create a folder with the following permissions
>$ mkdir test
>$ chmod g-w test
>$ ls -l
>drwxr-xr-x  2 dave dave  22 Jul 14 17:16 test
>
>When I create a file *within* this folder, and try to rename it I get a
>file permissions error.
>
>$ cd test
>$ touch asdf
>$ mv asdf asdf2
>mv: cannot move ‘asdf’ to ‘asdf2’: Permission denied
>
>A strace on the mv command reveals the rename system call fails with:
>rename("asdf", "asdf2") = -1 EACCES (Permission denied)
>
>However I can copy the file and delete the old one fine.
>
>If I either disable gluster root squashing, or change the test_dir
>folder
>group permission to write then I can rename the file without any
>problems.
>
>System details are:
>Arch linux
>System umask is set to 002
>Distributed volume, 3 peers, 1 brick per peer.
>
>Any help is much appreciated!
>Dave
>
>
>
>
>___
>Gluster-users mailing list
>Gluster-users@gluster.org
>http://supercolony.gluster.org/mailman/listinfo/gluster-users

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Remove Replica Pair issue.

2014-07-14 Thread Robert Moss 
Gluster Gurus,

I am having an issue removing a gluster replica pair. I have tried numerous 
different iterations of the command and get back 'Incorrect brick 
tx4-gluster1-10:/brick10 for volume gv0'
Here is the output of "gluster volume info":

Volume Name: gv0
Type: Distributed-Replicate
Volume ID: 176c0a15-c107-4bdc-9b00-df7e5c841374
Status: Started
Number of Bricks: 10 x 2 = 20
Transport-type: tcp
Bricks:
Brick1: tx4-gluster1-1:/brick1/brick
Brick2: tx4-gluster1-2:/brick1/brick
Brick3: tx4-gluster1-3:/brick1/brick
Brick4: tx4-gluster1-4:/brick1/brick
Brick5: tx4-gluster1-5:/brick1/brick
Brick6: tx4-gluster1-6:/brick1/brick
Brick7: tx4-gluster1-7:/brick1/brick
Brick8: tx4-gluster1-8:/brick1/brick
Brick9: tx4-gluster1-9:/brick1/brick
Brick10: tx4-gluster1-10:/brick1/brick
Brick11: tx4-gluster1-1:/brick2/brick
Brick12: tx4-gluster1-2:/brick2/brick
Brick13: tx4-gluster1-3:/brick2/brick
Brick14: tx4-gluster1-4:/brick2/brick
Brick15: tx4-gluster1-5:/brick2/brick
Brick16: tx4-gluster1-6:/brick2/brick
Brick17: tx4-gluster1-7:/brick2/brick
Brick18: tx4-gluster1-8:/brick2/brick
Brick19: tx4-gluster1-9:/brick2/brick
Brick20: tx4-gluster1-10:/brick2/brick
Options Reconfigured:
nfs.disable: off

I would like to remove gluster1-10 from the gluster cluster.
Here is my command:

gluster volume remove-brick gv0 replica 2 tx4-gluster1-10:/brick1 
tx4-gluster1-10:/brick2 force

Here is the result:
volume remove-brick commit force: failed: Incorrect brick 
tx4-gluster1-10:/brick1 for volume gv0

I have tried a number of iterations here, using different names and trying 
tx4-gluster1-10 and 1-9 bricks. Nothing has worked so far.
This is a test setup so we don't care about data, we just need to learn.
We will probably not put the node back in after removal.
Any help would be greatly appreciated.
Thank you in advance.

Best regards,

Rob Moss

___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Geo-replication failover and failback

2014-07-14 Thread Pranith Kumar Karampuri 

CCed relevant people.

Pranith
On 07/14/2014 07:00 PM, Mark Maas wrote:

Dear List,

Could someone perhaps point me (and others who find this) toward the
documentation for Geo-replication failover and faliback for Glusterfs
3.5 ?

I can find some old stuff from Redhat for 2.1

The best stuff is here:
https://github.com/gluster/glusterfs/tree/release-3.5/doc/admin-guide/en-US/markdown

Thanks!
Mark
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Geo-replication failover and failback

2014-07-14 Thread Mark Maas 
Dear List,

Could someone perhaps point me (and others who find this) toward the
documentation for Geo-replication failover and faliback for Glusterfs
3.5 ?

I can find some old stuff from Redhat for 2.1

The best stuff is here:
https://github.com/gluster/glusterfs/tree/release-3.5/doc/admin-guide/en-US/markdown

Thanks!
Mark
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Cannot rename files with root squashing and r-x folder group permissions

2014-07-14 Thread David Raffelt 
Hi All,
After a recent update to gluster 3.5 we are having some issues renaming
files when root squashing is enabled and the folder group permissions are
not set to write.

For example if I create a folder with the following permissions
$ mkdir test
$ chmod g-w test
$ ls -l
drwxr-xr-x  2 dave dave  22 Jul 14 17:16 test

When I create a file *within* this folder, and try to rename it I get a
file permissions error.

$ cd test
$ touch asdf
$ mv asdf asdf2
mv: cannot move ‘asdf’ to ‘asdf2’: Permission denied

A strace on the mv command reveals the rename system call fails with:
rename("asdf", "asdf2") = -1 EACCES (Permission denied)

However I can copy the file and delete the old one fine.

If I either disable gluster root squashing, or change the test_dir folder
group permission to write then I can rename the file without any problems.

System details are:
Arch linux
System umask is set to 002
Distributed volume, 3 peers, 1 brick per peer.

Any help is much appreciated!
Dave
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users