Re: [Gluster-devel] Read-only option for a replicated (replication for fail-over) Gluster volume

On Wed, Mar 22, 2017 at 2:31 AM, Mackay, Michael wrote: > At the risk of repeating myself, the POSIX file system underpinnings are > not a concern – that part is understood and handled. > > > > I’m also not asking for help to solve this problem, again, to be clear. > SE Linux

[Gluster-devel] How can add one fop after another fop?

Hi I want after create any file, do one setxattr automatically , where and how I should add this operation, and in which translator? ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Release 3.10.1: Scheduled for the 30th of March

On 03/27/2017 12:59 PM, Shyam wrote: Hi, It's time to prepare the 3.10.1 release, which falls on the 30th of each month, and hence would be Mar-30th-2017 this time around. We have one blocker issue for the release, which is [1] "auth failure after upgrade to GlusterFS 3.10", that we are

Re: [Gluster-devel] [Gluster-users] Proposal to deprecate replace-brick for "distribute only" volumes

On 03/16/2017 08:59 AM, Joe Julian wrote: In the last few releases, we have changed replace-brick command such that it can be called only with "commit force" option. When invoked, this is what happens to the volume: a. distribute only volume: the given brick is replaced with a empty brick with

Re: [Gluster-devel] Read-only option for a replicated (replication for fail-over) Gluster volume

I’m not sure if this went (email issues at the office), so re-sending. From: Mackay, Michael Sent: Tuesday, March 21, 2017 5:01 PM To: gluster-devel@gluster.org Subject: RE: (nwl) Re: [Gluster-devel] Read-only option for a replicated (replication for fail-over) Gluster volume At the risk of