Re: [Gluster-devel] Locating blocker bugs for a release (and what is a blocker anyway)

On 12 October 2017 at 10:12, Raghavendra Talur wrote: > On Wed, Oct 11, 2017 at 8:35 PM, Shyam Ranganathan > wrote: > > Hi, > > > > Recently I was in some conversations that mentioned having to hunt for > the > > mail that announced the blocker bug for a

Re: [Gluster-devel] Locating blocker bugs for a release (and what is a blocker anyway)

On Wed, Oct 11, 2017 at 8:35 PM, Shyam Ranganathan wrote: > Hi, > > Recently I was in some conversations that mentioned having to hunt for the > mail that announced the blocker bug for a release, when there is a need to > mark a bug as a blocker for that release. > > This

Re: [Gluster-devel] [Gluster-Maintainers] Client Server incompatibility with Gluster 4.0

On Wed, Oct 11, 2017 at 5:06 AM, Amar Tumballi wrote: > Was (Re: [Gluster-devel] Proposed Protocol changes for 4.0: Need feedback.) > > All, > > While we are at making all the below tasks' color coding to GREEN, it > would make sense to discuss 1 main thing. > > With 4.0, we

[Gluster-devel] tendrl-release v1.5.3 (bugfixes) is available

Hello, The Tendrl team is happy to present tendrl-release v1.5.3 (bugfixes) Install docs: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.3-(install-guide) Metrics: https://github.com/Tendrl/documentation/wiki/Metrics ___

Re: [Gluster-devel] Report ESTALE as ENOENT

On Wed, Oct 11, 2017 at 07:26:43AM -0400, Raghavendra Gowdappa wrote: > Another place to not convert is for those cases where kernel retries the > operation on seeing an ESTALE. > > I guess we need to think through each operation and we cannot ESTALE to > ENOENT always. By the way, my advice

Re: [Gluster-devel] Report ESTALE as ENOENT

We ran into a regression [2][3]. Hence reviving this thread. [2] https://bugzilla.redhat.com/show_bug.cgi?id=1500269 [3] https://review.gluster.org/18463 On Thu, Mar 31, 2016 at 1:22 AM, J. Bruce Fields wrote: > On Mon, Mar 28, 2016 at 04:21:00PM -0400, Vijay Bellur

[Gluster-devel] Locating blocker bugs for a release (and what is a blocker anyway)

Hi, Recently I was in some conversations that mentioned having to hunt for the mail that announced the blocker bug for a release, when there is a need to mark a bug as a blocker for that release. This need not be done as here is the shortcut (if you did not know) on how to find the blocker,

[Gluster-devel] Community Meeting 2017-10-11

We had a quick meeting today, with 2 main topics. We have a new community issue tracker [1], which will be used to track community initiatives. Amye will be sharing more information about this in another email. To co-ordinate people travelling to the Gluster Community Summit better, a

Re: [Gluster-devel] [Gluster-users] Gluster CLI Feedback

Hi, I have only a feedback to point 4/5. Despite using http://docs.ansible.com/ansible/latest/gluster_volume_module.html for gluster management I see the operation of replacing a server with a new hardware while keeping the same IP number poorly documented. Maybe I was just unlucky in my search

[Gluster-devel] Coverity covscan for 2017-10-11-34d52445 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-11-34d52445 ___ Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] Report ESTALE as ENOENT

We ran into a regression [2][3]. Hence reviving this thread. [2] https://bugzilla.redhat.com/show_bug.cgi?id=1500269 [3] https://review.gluster.org/18463 - Original Message - > From: "J. Bruce Fields" > To: "Vijay Bellur" > Cc: "Gluster Devel"

Re: [Gluster-devel] Report ESTALE as ENOENT

On Wed, Oct 11, 2017 at 04:11:51PM +0530, Raghavendra G wrote: > On Thu, Mar 31, 2016 at 1:22 AM, J. Bruce Fields > wrote: > > > On Mon, Mar 28, 2016 at 04:21:00PM -0400, Vijay Bellur wrote: > > > I would prefer to: > > > > > > 1. Return ENOENT for all system calls that

[Gluster-devel] Note on github issue updates from gluster-ant

Hi, Currently, when a new change is posted referencing a github issue, an automated message is posted on the issue by gluster-ant. Further, if the patch is refreshed for any reason, another message with the same content is posted on the issue by gluster-ant. The above causes noise, and also

[Gluster-devel] Client Server incompatibility with Gluster 4.0

Was (Re: [Gluster-devel] Proposed Protocol changes for 4.0: Need feedback.) All, While we are at making all the below tasks' color coding to GREEN, it would make sense to discuss 1 main thing. With 4.0, we will anyways say 3.y series server nodes are not going to be compatible with 4.x servers,

[Gluster-devel] Gluster CLI Feedback

Hi, As part of our initiative to improve Gluster usability, we would like feedback on the current Gluster CLI. Gluster 4.0 upstream development is currently in progress and it is an ideal time to consider CLI changes. Answers to the following would be appreciated: 1. How often do you use the